revert dropping crc32c

[d-v-b]

Zarr python 3.1.3 indirectly depends on numcodecs for crc32c. Thanks to #792, zarr python can no longer import crc32c which breaks zarr python. We should revert #792 and issue an immediate release.

[jhamman]

I do not think reverting #792 is the right choice. The issue was that Zarr-Python was incorrectly depending on this implicit dependency. Users can solve this today by installing crc32c in addition to zarr-python. Going forward, zarr-python should be sure to specify any dependencies that it imports.

[d-v-b]

whether or not it was incorrect for zarr-python to depend on an indirect dependency, people using zarr python 3.1.3 will have their code break if they update numcodecs. I think that's worth fixing!

[jhamman]

Let's "fix" it in zarr-python 3.1.4 by specifying the missing dependency.

[d-v-b]

i am really motivated to keep things working for people who are not interested in update zarr python. the idea of breaking code that used to work doesn't sit well with me. I think we can have the best of both worlds via #802, which keeps the old crc32c extra and puts the google crc32c in its own separate extra dep. please take a look and let me know what you think

[ShrimpCryptid]

Glad there's an issue for this! I just had a bunch of CI/CD workflows fail unexpectedly because of this change as well, though I probably should be pinning my dependency versions to avoid this in the future.

[maxrjones]

This was fixed in the v0.16.5 release via #802.