feat: add from_array_metadata_and_store to CodecPipeline

[LDeakin]

This enables the zarrs-python CodecPipeline to support a broader range of Zarr arrays and to construct store wrappers on initialisation. I've tried to write this so that it is an entirely non-breaking change.

I've trialled this here zarrs/zarrs-python@263a55c.

xref:

• Investigate Rust-Based Python-Accessed Stores zarrs/zarrs-python#64 (comment)

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/*.rst
• 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 94.76%. Comparing base (ea4d7e9) to head (306d040).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3233   +/-   ##
=======================================
  Coverage   94.76%   94.76%           
=======================================
  Files          78       78           
  Lines        8710     8718    +8     
=======================================
+ Hits         8254     8262    +8     
  Misses        456      456           

Files with missing lines	Coverage Δ
src/zarr/abc/codec.py	93.93% <100.00%> (+0.28%)	⬆️
src/zarr/core/array.py	98.53% <100.00%> (+<0.01%)	⬆️

🚀 New features to boost your workflow:

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

[d-v-b]

looks good! I had 1 suggestion about making the store argument keyword-only