• Requires feat: add from_array_metadata_and_store to CodecPipeline zarr-developers/zarr-python#3233 which looks like it will release with zarr-python 3.1
• Needs chore: handle new zarr dtype API #100
• Should unblock Investigate Rust-Based Python-Accessed Stores #64 (e.g. obstore support).

This simplifies a lot, removes the StoreManager and lets us properly support a broader range of arrays where codec behaviour is dependent on non-codec metadata (e.g. data_type, order).

I added a warning that indicates to a user why an array is not supported by zarrs when constructing a ZarrsCodecPipeline. This catches a few things and reveals some holes in zarrs support for Zarr V2 data which can be supported eventually. Features that aren't supported by zarrs-python, like variable sized data types, still just silently fallback at runtime.