iohub convert writing to both highest resolution scale metadata and highest level

[edyoshikun]

From our discussion on mantis and the metadata scaling @talonchandler @ziw-liu , I have found that iohub converts and adds the scale metadata to both the top of the 'pyramid' and the highest resolution level.

Should the normal behavior be to write into the datasets dictionary rather than the higher level coordinateTransformation as shown below or should the the highest level (top of pyramid) always be "scale":[1,1,1,1,1]" Since the ngff.Position.scale, always looks for the highest resolution, then shouldn't we leave the top level of the pyramid to be untouched (?)

            "coordinateTransformations": [
                {
                    "scale": [
                        1.0,
                        1.0,
                        0.143,
                        0.1494,
                        0.1494
                    ],
                    "type": "scale"
                }
            ],
            "datasets": [
                {
                    "coordinateTransformations": [
                        {
                            "scale": [
                                1.0,
                                1.0,
                                0.143,
                                0.1494,
                                0.1494
                            ],
                            "type": "scale"
                        }
                    ],

/hpc/projects/comp.micro/mantis/2023_08_09_HEK_PCNA_H2B/0-zarr/pcna_rac1_virtual_staining_1/pcna_rac1_virtual_staining_labelfree_1.zarr/0/0/0/.zattrs