Add compatibility with Zarr-Python 3.2.0

[maxrjones]

There are some internal changes coming in Zarr-Python that impact VirtualiZarr, which are addressed by this PR.

Acceptance criteria:

• Closes #xxxx
• Tests added
• Tests passing
• No test coverage regression
• Full type hint coverage
• Changes are documented in docs/releases.md
• New functions/methods are listed in an appropriate *.md file under docs/api
• New functionality has documentation

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.34%. Comparing base (ce729ca) to head (3129388).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #957      +/-   ##
==========================================
+ Coverage   89.30%   89.34%   +0.03%     
==========================================
  Files          33       33              
  Lines        2039     2046       +7     
==========================================
+ Hits         1821     1828       +7     
  Misses        218      218              

Files with missing lines	Coverage Δ
virtualizarr/manifests/array.py	85.00% <100.00%> (+0.62%)	⬆️
virtualizarr/parsers/zarr.py	97.50% <100.00%> (+0.04%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[maxrjones]

failures should be fixed upstream by earth-mover/icechunk#1937

[TomNicholas]

failures should be fixed upstream by earth-mover/icechunk#1937

Note that this is only for Icechunk 2.0. We actually have the same problem for the latest release of IC 1.0 . But do we care about that?

[TomNicholas]

Also can we perhaps release a patch version of VZ first? We have multiple things going on here:

• Broken sharding feature already released that needs patching
• Compatibility with IC2 (should work out of the box, but should we pin for any reason?)
• Your changes in this PR

[maxrjones]

failures should be fixed upstream by earth-mover/icechunk#1937

Note that this is only for Icechunk 2.0. We actually have the same problem for the latest release of IC 1.0 . But do we care about that?

I think that any release of Icechunk with a fix for the missing readme would solve our CI problems, as long as we don't pin to <2.

[maxrjones]

Also can we perhaps release a patch version of VZ first? We have multiple things going on here:

• Broken sharding feature already released that needs patching
• Compatibility with IC2 (should work out of the box, but should we pin for any reason?)
• Your changes in this PR

I'd support merging and releasing #952 before any other changes. fwiw I don't think it's bad to have merged #897 before the patch release - that's a long overdue bug fix.

[TomNicholas]

I think that any release of Icechunk with a fix for the missing readme would solve our CI problems, as long as we don't pin to <2.

That release should come in a sec / by tomorrow.

I'd support merging and releasing #952 before any other changes. fwiw I don't think it's bad to have merged #897 before the patch release - that's a long overdue bug fix.

Agreed.

[TomNicholas]

Released, so as long as this passes (particularly on min-deps!) then lets go

[TomNicholas]

Maybe we should actually look for specific versions of zarr-python instead of the blind try...except?