Support multiple zarr backends + abstraction

[balbasty]

I feel like it would be good to have an option to switch between zarr/zarrita/tensorstore for the zarr i/o, as they all have pros and cons and this would enable benchmarking each of them.

The most useful think would probably to abstract away the few features that we actually use (opening/writing a group, opening/writing/slicing an array), and wrap each of the libraries in classes that inherit from this AbstractZarrIO class.

[kabilar]

Just noting that zarr-python version 3 was released yesterday.

• Release notes - https://github.com/zarr-developers/zarr-python/releases/tag/v3.0.0
• Blog post - https://zarr.dev/blog/zarr-python-3-release/