Make use of get_zarr_format_version to provide version of zarr

[yarikoptic]

defined but not used, I guess missed that during PR review

❯ git grep get_zarr_format_version
dandi/files/zarr.py:def get_zarr_format_version(data: Any) -> str:

detected while reviewing code for

• zarr 3 support #1609

[candleindark]

I defined it in #1514. However, I ended up not using it because there is no need at this point. The points in the code used to need this have a corrected origin of ORIGIN_VALIDATION_DANDI_ZARR, such as

dandi-cli/dandi/files/zarr.py

Line 276 in 88c3275

origin=ORIGIN_VALIDATION_DANDI_ZARR,

. I was keeping to function for future use.

However, upon working on #1609, I discovered that get_zarr_format_version is not able to handle the final or experimental Zarr V3 Specification correctly. I can either remove the function entirely or add the handling of Zarr V3 Specification at this point. For support for deciding Zarr V1 Specification, will be a bit tricky. I think will need to try much older version of Zarr to see what the file formats are like.

[yarikoptic]

before we jump to v3, for which we could add a test if there is zarr.json and get zarr_format from it, it doesn't work even for v2 of zarr like those we already have in the archive , e.g.
https://dandiarchive.s3.amazonaws.com/zarr/001e3b6d-26fb-463f-af28-520a25680ab4/.zmetadata?versionId=lFCKAw3nHHT66S14.hEaGXm9sBL9eYvW where it says "zarr_format": 2?

[yarikoptic]

anyways -- we should strive to provide that standard_version for Zarr "files". Yes -- ideally should come from zarr library (file an issue?) but if there is no way there, we should implement some.

[github-actions]

🚀 Issue was released in 0.68.0 🚀