Fix multiscale examples

[jo-mueller]

Mirror PR to carry ome/ngff#311 over to ngff-spec. Can be merged once that ome/ngff#311 has been merged, too, to make sure both places stay in sync and that @mkitti's contribution is acknowledged in the commit history.

Co-pilot description

This pull request updates several NGFF multiscales example JSON files to standardize dataset path naming and improve the representation of coordinate systems and transformations. The most significant changes include renaming dataset paths from numeric values to string identifiers (e.g., "0" → "s0"), updating transformation input references accordingly, and enhancing the structure for specifying coordinate systems in the multiscales metadata.

Standardization of dataset paths and input references:

• Changed dataset path fields from numeric strings (e.g., "0", "1", "2") to string identifiers ("s0", "s1", "s2") in multiscales_example.json, multiscales_example_relative.json, and multiscales_transformations.json. Updated all corresponding input fields in coordinateTransformations to match the new path names. [1] [2] [3] [4]

Enhancements to coordinate system specification:

• Added a coordinateSystems section to the multiscales metadata in multiscales_transformations.json, explicitly defining the "intrinsic" coordinate system and its axes. [1] [2]

Other metadata improvements:

• Updated the multiscales name field in multiscales_transformations.json from "image_with_coordinateTransformations" to "image_with_multiscaleTransformations" for clarity and consistency.

[github-actions]

Automated Review URLs

• Readthedocs