Deprecate (Async)Array.create

[normanrz]

Builds upon #2463

• Deprecates AsyncArray.create and Array.create to Array._create including deprecation warnings in favor of zarr.create_array.
• Adds AsyncArray._create and Array._create which now contain the code of the unprefixed methods. We should not use them for new code anymore and remove once other APIs have been deprecated and removed.

I added 2 new features to make create_array usable for all codec configurations I could think of:

• Adds a dict-notation to the shards kwarg in create_array to specify the index location, e.g. shards={"shape": (32, 32), "index_location": "start"}
• Adds an optional array_bytes_codec kwarg to create_array to override the array-to-bytes codec for v3 arrays, e.g. to specify the endianness.

[d-v-b]

I think this parameter is important, but I think we can do better with the name to express a bit more what it does, and detach the name from the type (which might change). Unfortunately the only ideas I have are array_serializer chunk_serializer but I'm sure there are better options.

[normanrz]

What about just codec?

[d-v-b]

to me, codec is a category that includes ArrayBytesCodec and BytesBytesCodec; I think the ideal name would somehow convey that this entity is tasked with unpacking (or packing?) an array into bytes. chunk_<verb>+er seems like a good template, but I'm not sure what verbs fit well here. 🤔 chunk_serializer, chunk_packer, chunk_streamer... chunk_serializer seems the best to me but it's far from great.

[normanrz]

I think chunk_serializer is fine.
Maybe even just serializer. That would be more in line with filters and compressors.

[d-v-b]

+1 to dropping chunk_ as long as we don't think people will be confused about the scope

[d-v-b]

This looks great! But I do think we should try to improve the name of the array_bytes_codec kwarg. see #2607 (comment)

[jhamman]

lgtm, thanks @normanrz

[normanrz]

Merged into #2463.