feat(demo): add button to reproduce labelmap removal crash

[theoc0702]

Context

This PR shows a crash that occurs when removing a segmentation representation from a MIP (Maximum Intensity Projection) viewport.
In the SEGMENTATION_REPRESENTATION_REMOVED event listener, the code attempts to immediately re-create a volume actor using createVolumeActor. However, it passes the uid (which is the Actor UID being removed) as the volumeId.
For derived volumes (like labelmaps generated in memory), this incorrect ID causes volumeLoader to fail, often throwing the error: Error: ImageIds must be provided to create a streaming image volume. This happens because the loader cannot find the derived volume by that ID and falls back to the streaming loader, which requires ImageIds.

Changes & Results

Added a button for trying to delete the Labelmap eepresentation and cause the error.

Testing

In the example labelmapMip, add a Labelmap Representation then click on the button "Delete Labelmap Representation" wich try to delete the labelmap and shows the error

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

• "OS: Ubuntu v24.04.3 LTS
• "Node version: v24.11.0
• "Browser: Chrome Version 143.0.7499.169

[salimkanoun]

This PR is to demonstrate a bug we found, we didn't succeed to understand the logic to fix the bug

[wayfarer3130]

When I try it, it goes all weird:

[wayfarer3130]

This appears to be an empty change based on the 3.12 release version. Can you close, or else look at the purple background issue I posted in the comments/

[salimkanoun]

@wayfarer3130 the initial bug is fixed,

The other bug I have is when I remove the segmentation I loose my SlabThinkness see :
Screencast from 2026-02-19 23-09-29.webm

However it is probably another bug, can we merge this PR to get this button to remove segmentation and then we will see what we can do on this viewport property loss