future proofing ez-zarr

[mbstadler]

These are a few changes that will keep ez-zarr functioning with future version of

• python (changes to the pyproject.toml file format, specifically related to how the license is specified, see https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license)
• pandas v3.0, which will change copy-on-write behavior when assigning values to a data frame (see chained assignments: https://pandas.pydata.org/docs/user_guide/copy_on_write.html#copy-on-write-chained-assignment).

Maybe worth before merging this:

• should we bump the version?
• are there any other maintenance tasks to do?

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (2bc0aa9) to head (484ef6f).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #51   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines         1206      1206           
=========================================
  Hits          1206      1206           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

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

[csoneson]

This is great, thank you! I can't immediately think of any other maintenance tasks that would be relevant right now, and I would vote to bump the version 🙂

[mbstadler]

Thanks a lot - I'll go forward then and create a new release