Code examples should be JSONC rather than JSON

The examples contain JavaScript comments in them. JSON does now allow for comments. JSONC does allow for comments.

Notice how the comment here is highlighted in red.

{
  "zarr_format": 3,
  "node_type": "group",
  "attributes": {
    "ome": {
      "version": "0.5",
      "multiscales": [
        {
          "name": "example",
          "axes": [
            { "name": "t", "type": "time", "unit": "millisecond" },
            { "name": "c", "type": "channel" },
            { "name": "z", "type": "space", "unit": "micrometer" },
            { "name": "y", "type": "space", "unit": "micrometer" },
            { "name": "x", "type": "space", "unit": "micrometer" }
          ],
          "datasets": [
            {
              "path": "0",
              "coordinateTransformations": [
                {
                  // the voxel size for the first scale level (0.5 micrometer)
                  "type": "scale",
                  "scale": [1.0, 1.0, 0.5, 0.5, 0.5]
                }
              ]
            }
          ]
        }
     ]
    }
  }
}

If we code this as JSONC, the Github syntax highlighter is more forgiving.

{
  "zarr_format": 3,
  "node_type": "group",
  "attributes": {
    "ome": {
      "version": "0.5",
      "multiscales": [
        {
          "name": "example",
          "axes": [
            { "name": "t", "type": "time", "unit": "millisecond" },
            { "name": "c", "type": "channel" },
            { "name": "z", "type": "space", "unit": "micrometer" },
            { "name": "y", "type": "space", "unit": "micrometer" },
            { "name": "x", "type": "space", "unit": "micrometer" }
          ],
          "datasets": [
            {
              "path": "0",
              "coordinateTransformations": [
                {
                  // the voxel size for the first scale level (0.5 micrometer)
                  "type": "scale",
                  "scale": [1.0, 1.0, 0.5, 0.5, 0.5]
                }
              ]
            }
          ]
        }
     ]
    }
  }
}

No file or test is named; search the repository's documentation examples for fenced blocks labeled json that contain comments. Change the relevant fences to jsonc, then inspect the rendered examples on GitHub to confirm that comments are highlighted correctly.