[LKasianAnsys]

Issue

Addresses #28

Context

Until now, the server mode visualizer showed the streamed frames but no UI panels. This PR adds the panels on top of the server-mode canvas, and adds a client-side ServerRenderer by sending each panel action to the server as a trigger, so the panel controls work in server mode. See the copilot summary below for a more complete summary of the changes.

Key Changes:

• Created ServerRenderer which implements IRenderer
• Triggers are moved into SceneTriggerSends
• Server mode now builds a VisorFrontnend so the panels appear, and sends set_dark_theme on each build.

Manual check:
Start VISOR in server mode with a dataset. Check that the panels now appear. Test hiding a part, toggling the bounding box, and toggling the cross-section widget. Note that these panels do not yet update after an add_dataset API call from the backend: that is addressed in user story 4.4 (#29).

Copilot summary

This pull request introduces significant improvements to the server-rendering ("remote rendering") mode in the Visor client, focusing on integrating the panel UI in server mode, refactoring the server-rendering frontend construction, and adding robust tests for server-rendering behavior. The changes simplify the code by removing the need to manually mount the server canvas, update type definitions, and enhance test coverage for both the renderer and the React hook responsible for server mode.

Key changes include:

Server Rendering Integration and Refactoring:

• The panel UI is now displayed in server-rendering mode, aligning the user experience with local rendering. The useServerVtk hook has been refactored to build the full visorFrontend (including UI panels) instead of just exposing a canvas, and the manual canvas mounting logic in App.tsx has been removed. [1] [2] [3] [4]
• The useServerVtk hook now manages the lifecycle and cleanup of the server renderer and frontend, ensuring proper resource management and error handling for schema mismatches.

Type and Interface Updates:

• Renderer-related types have been updated: CameraSyncSource now references WasmRenderer instead of the broader IRenderer, and the addCameraSettledListener method has been removed from IRenderer and related implementations, as it is not relevant for server rendering. [1] [2] [3] [4] [5] [6] [7]

Testing Enhancements:

• New tests verify the correct construction and behavior of the server-rendering frontend, including toolbar actions and theme propagation. These tests ensure that UI actions are correctly sent to the server and that the dark theme is communicated as expected. [1] [2] [3]
• Additional tests for ServerRenderer confirm the correct caching and toggling of camera and widget states, improving confidence in server-rendering correctness.

Test and Mock Updates:

• Existing tests have been updated to match the new server-rendering flow, particularly in how triggers are handled and how the frontend is constructed for testing purposes.