Update dependency Blosc/c-blosc2 to v3.2.3

[wongcht]

This PR contains the following updates:

Package	Update	Change
Blosc/c-blosc2	patch	3.2.1 → 3.2.3

---

Release Notes

Blosc/c-blosc2 (Blosc/c-blosc2)

v3.2.3

Compare Source

===========================

#XXX version-specific blurb XXX#

Bug fixes

• Fixed wrong results in schunk slice and sparse reads for typesize > 255.
  blosc2_schunk_get_slice_buffer() derived its blosc2_getitem_ctx()
  item counts by dividing byte offsets by schunk->typesize, but chunks
  whose typesize exceeds BLOSC_MAX_TYPESIZE (255) are compressed with an
  internal typesize of 1, so getitem counts bytes for them. Slices that did
  not cover a chunk exactly mostly failed with BLOSC2_ERROR_FAILURE, and
  single-element slices returned the wrong bytes with a success return code.
  The single-coordinate path of blosc2_schunk_get_sparse_buffer() had the
  same confusion. Both now convert through the chunk's actual item unit.
  See #​796.

• blosc2_getitem_ctx() now returns BLOSC2_ERROR_DATA instead of a
  short byte count when it cannot decode every requested item, so a partial
  decode no longer looks like a success to callers that only test for a
  negative return.

v3.2.2

Compare Source

===========================

Bug fixes

• Fixed data corruption in b2nd get_slice for typesize > 255. The
  compact get path introduced in 3.2.2 passed item counts to
  blosc2_getitem_ctx() in array-typesize units, but chunks whose
  typesize exceeds BLOSC_MAX_TYPESIZE (255) are compressed with an
  internal typesize of 1, so small slice reads returned truncated blocks
  (only the first blocknitems bytes were correct). Item counts are
  now expressed in the chunk's actual item unit, keeping the fast path
  both correct and O(request) for large typesizes. Added a regression
  test covering typesize > 255 on the get_slice path.

Notes

• This is a hot-fix release with no API/ABI changes. Users of 3.2.2
  reading slices from b2nd arrays with typesize > 255 should upgrade.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.