Pack Zarr-related config into a dataclass

[calvinchai]

The use of this dataclass is dummy now, but it will be used when we started to use the AbstractZarrIO class and used to initialize the class instance

[balbasty]

This looks great.

One thing I was wondering so that we can keep using the previous functional api (I.e be able to pass convert(..., out=...)) is whether we should let convert accept additional **kwargs and pass these kwargs to the zarr_config if they exist.

Something like zarr_config = replace(zarr_config, kwargs) as in this stackoverflow: https://stackoverflow.com/questions/52556605/update-a-field-in-a-dataclass-with-a-field-name-known-only-during-runtime/53029448#53029448

[calvinchai]

Yes, we can probably do that for each conversion function at the begining and pack that into a function for reuse. The only downside I see of for now after trying add it is that it will make the function intake arbitrary arguments and we need to check the argument one by one since replace will panic if a unknown parameter exists.