chore(zarr-metadata): bump version to 0.1.1

[d-v-b]

version 0.1.0 is burned on pypi in order to namesquat the package. so the first version we can publish will be 0.1.1.

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.md
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.23%. Comparing base (80d45ca) to head (f1e59f6).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3949   +/-   ##
=======================================
  Coverage   93.23%   93.23%           
=======================================
  Files          87       87           
  Lines       11696    11696           
=======================================
  Hits        10905    10905           
  Misses        791      791           

🚀 New features to boost your workflow:

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

[ilan-gold]

we use https://github.com/ofek/hatch-vcs with a decent amount of success! This might explain why I think dev commit hashes are suffixed by default on to versions, hence my comment in #3935 (comment).

[d-v-b]

We are also using vcs versioning but for zarr python. As this package is versioned independently, we will to add some logic to the git tag -> version string workflow to ensure that zarr python release tags are distinct from zarr metadata release tags

[ilan-gold]

Got it, I see that now.