Update Embassy URLs to use new Embassy Cloud object storage

[sbesson]

See https://forum.image.sc/t/hcs-ome-zarr-data-unable-to-download/57114/6

The current S3 URLs are regularly hitting 503 errors which might be related to the fact these resources are being EOL'ed.

The three OME-Zarr samples have been sync'ed to the new Embassy Cloud v4 storage.

Opening this PR as a prererequisite of the overall migration

[joshmoore]

Thanks, @sbesson. I still have some hope for the redirects from s3.*, but this does raise a long-term question. Not sure if it wouldn't be safer to go with our own proxy (like idr-analysis).

[sbesson]

I agree that if we are going to tell our community they need to change their URLs/bookmarks, we might want to ensure they only update once.

As a starting point, there is some proxying infrastructure already in place with idr-s3.openmicroscopy.org (see IDR/deployment#280). We could certainly try to build on top of that (potentially move it as part of the prodXX-proxy) and test it in various context.

[imagesc-bot]

This pull request has been mentioned on Image.sc Forum. There might be relevant details there:

https://forum.image.sc/t/ome-zarr-support-in-fiji/57296/3

[joshmoore]

Merging this to have things more stable, but we may want to re-address with a proxy in the future.