Offer the option in high-level APIs to write xarray-compatible zarr stores

[emileten]

Currently, by default, we write 'raw' zarr arrays without the coordinate labels in the metadata, which makes the output unusable natively with xarray. However, we do have methods in this code base to write xarray-compatible zarr stores from the output we produce. See context : #66.

This ticket is about adding options to the module's APIs (namely, the command line interface and services API) to actually make use of this existing method and ensure the output of a given run is readable with xarray.