[LKasianAnsys]

Issue

Addresses #192

Summary

In a future PR, the client and server rendering modes will share a mechanism for geometry picking and highlighting. Client mode will be updated to use the new server-mode geometry picking mechanism. This will introduce a round trip from the client to the server on every geometry pick. However, before introducing these round trips, we first need an optimization.

Until now, every server push in client mode applied its update to the wasm scene and then rebuilt the frontend, and the pushes could overlap. With this PR, updates now run one in series, and pushes that arrive during one merge into a single pending update, which rebuilds once if any of them was structural.

Changes (client mode only; server mode is unaffected)

• Server updates now go through a new SerialUpdateQueue and run one at a time.
• Pushes that arrive while an update is running merge into one pending update. The latest options win, and every caller gets the same promise. The frontend rebuilds once if any merged push was structural.
• An update sent with dataOnly is applied and redrawn without a frontend rebuild. This is parsed by the new WasmUpdateOptions.
• A failed update skips its rebuild and does not block the next one.

Files

• RemoteVtkScene.js: updateAsync now goes through the queue. The apply and listener-notify steps are split out.
• SerialUpdateQueue.ts and WasmUpdateOptions.ts: new.
• Unit tests cover the queue and the option parsing.

[ansBAkula]

Tested and no regressions on client side functionality.