fix(jump-to-label-map): Handle case in getReferenceVolumeForSegmentationVolume where the volume is built from the segmentation's image IDs.

[jbocce]

Context

See OHIF issue OHIF/Viewers#5771

Changes & Results

Handle case in getReferenceVolumeForSegmentationVolume where the volume is built from the segmentation's image IDs.
In VolumeViewport.jumpToWorld, do not jump to the world position if it is outside the bounds of the volume.

The full fix in OHIF requires both this PR and OHIF PR OHIF/Viewers#5774

Testing

See OHIF issue OHIF/Viewers#5771

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.)

Public Documentation Updates

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

Tested Environment

System:
OS: Windows 11 10.0.26200
CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
Memory: 6.49 GB / 31.68 GB
Binaries:
Node: 23.9.0 - C:\Users\joebo\AppData\Local\fnm_multishells\14076_1770140411794\node.EXE
Yarn: 1.22.22 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 10.9.2 - C:\Users\joebo\AppData\Local\fnm_multishells\14076_1770140411794\npm.CMD
bun: 1.2.23 - C:\Users\joebo.bun\bin\bun.EXE
Browsers:
Chrome: 144.0.7559.110

[wayfarer3130]

Could you just update the comment?
Otherwise I understand what you are doing - we need a better way to ask the question about getting volumes - could you test with stack viewports to make sure it works there?

[wayfarer3130]

Actually, I'd like to test a few things as to how they work.

[jbocce]

Actually, I'd like to test a few things as to how they work.

Yup. NP.

[wayfarer3130]

Tested a number of scenarios. Although I can cause it to jump to something not visible, that is a separate issue not affected by this PR.