Support different output storage schemes of reformatting workflow

[mario-winkler]

The reformatting workflow now supports two ouput storage schemes:

• s3 (current) where the Zarr store is put as is into object storage
• zip (new) where the data is stored as zipped Zarr store and data access is proxied through the Zarr API service

Since the storage scheme affects the content of the STAC item asset hrefs, eopf-stac needs to know which storage scheme is used by the reformatting workflow.

Therefore, add a new CLI parameter --storage-scheme with the valids s3 (default) and zip.