[LKasianAnsys]

Issue

Addresses #192

Summary

Until now, geometry picking has had two separate implementations: client mode picked in WASM and drew the highlight on a narrow canvas overlay, and server mode picked and highlighted on the server. This PR moves client mode onto the server-mode implementation. It also fixes a VTK object id clash between the browser and the server in client mode.

Changes

• Server-side pick and highlight: The client now asks the server to set and clear the highlight. The server draws it in the shared scene and pushes it as a data-only update.
• Pixel ratio: The client reports its device pixel ratio (new pixel_scale payload). The highlight then matches server mode in size.
• Overlay removed: The WASM picking code and the canvas overlay are gone from VtkScene.js, LocalRenderer and LocalScene.
• Picked actor read: The picked actor is now read with an invoke call (GetActor) instead of a property read.
• Highlight with edges on: Highlights were hidden behind part faces when edge visibility was on. Parts now get a small polygon offset so the highlight draws in front.
• Resize guards: The WASM window is no longer resized when the canvas is 0×0 or its size hasn't changed.
• Object id clash fix: The browser and the server allocate VTK object ids from one counter range. An id the browser allocated itself could be handed out again by the server's next new object, and the deserializer would then apply the server's state to the wrong object. Right after the wasm module loads, and before any other wasm call, RemoteVtkScene now registers one vtkPoints at id 2 ** 30 (then unregisters its state). Registering at an explicit id raises the counter, and it never falls, so every id the browser allocates afterwards lands above the server's range.

Tests Unit and Jest tests are updated or added for the new flow. Tests for the removed WASM picking code are deleted. A new Jest test (RemoteVtkSceneIdFloor) pins that the id registration at 1073741824 is the first wasm call after load.

Manual testing

The client and server rendering modes now share a geometry picking and highlight mechanism. Test in both modes and they should look and behave the same way.

Id clash check (client mode): Load the viewer with the browser console open at the default level. Pick geometry repeatedly, and call scene-modifying APIs such as add_dataset between picks. Expect no crash and no wrong-object updates, and no console warning starting with Error in WebAssembly module or Could not reserve the browser id range.