docs(Example): Update Segmentation Volume

[jlopes90]

Context

Changes & Results

Testing

Example Segmentation Volume
https://deploy-preview-1201--cornerstone-3d-docs.netlify.app/live-examples/segmentationVolume.html

Checklist

PR

• [] My Pull Request title is descriptive, accurate and follows the
  semantic-release format and guidelines.

Code

• [] My code has been well-documented (function documentation, inline comments,
  etc.)

• [] I have run the yarn build:update-api to update the API documentation, and have
  committed the changes to this PR. (Read more here https://www.cornerstonejs.org/docs/contribute/update-api)

Public Documentation Updates

• [] The documentation page has been updated as necessary for any public API
  additions or removals.

Tested Environment

• [] "OS:
• [] "Node version:
• [] "Browser:

[netlify]

✅ Deploy Preview for cornerstone-3d-docs canceled.

Name	Link
🔨 Latest commit	dd9c514
🔍 Latest deploy log	https://app.netlify.com/sites/cornerstone-3d-docs/deploys/6619653886c3e700097a9e3e

[jlopes90]

Don't merge yet, only when I say

[jlopes90]

@sedghi

Before

When loading dicom and segmentation, the segmentation is opposite or incorrect.

async function fetchDicom() {
    imageIds = await createImageIdsAndCacheMetaData(exConfig.fetchDicom);
    await loadDicom(imageIds);
}

After

I changed the loadDicom(imageIds) to loadDicom(imageIds.reverse()), this is dicom loading.
When loading dicom and segmentation, the segmentation is correct.

async function fetchDicom() {
    imageIds = await createImageIdsAndCacheMetaData(exConfig.fetchDicom);
    await loadDicom(imageIds.reverse());
}

But why?

[l5769389]

bug like the link #1170 (comment)

[l5769389]

@jlopes90， i find reverse the imageIds can match as you said。 bug will cause the segmentation and volume mismatch in volume render。as the figure after i reverse the imageIds。 left mpr 3 viewers works，but right error。