zarr-metadata tags break zarr tag-based versioning

[d-v-b]

zarr-metadata releases are associated with a special git tag that starts with zarr-metadata-<version>. When generating a runtime version string from a git tag, zarr reads the zarr-metadata tag and reports that as its version, leading to zarr reporting it's current version as 0.2.0.dev....

To fix this, we need zarr to exclude zarr-metadata-<version> tags in its hatch-vcs configuration.

[d-v-b]

see https://github.com/zarr-developers/zarr-python/actions/runs/26187664671/job/77047478983?pr=3992