feat: [Remote rendering 3.5b] client uses server owned variables

[LKasianAnsys]

Issue

Addresses #23

Status: WIP

Copilot summary

This pull request refactors how variable metadata and range information are managed and delivered between the server and client in the Visor application. The changes move ownership of variable records from the client to the server, ensuring that variable state is always sourced from server deliveries rather than being reconstructed or duplicated on the client. The update also simplifies the flow for updating and applying variable ranges, and introduces new utility methods for UI components to refresh their state based on the latest variable records.

Key changes include:

Variable Record Ownership & Delivery

• Removed client-side reconstruction of variable records during scene rebuilds; now, variable records are always delivered by the server and not carried over or duplicated on the client. (VisorFrontend.tsx, VisorVariableManager.tsx) [1] [2]
• Updated VisorVariableManager to provide methods for setting delivered variable records (setRecords) and projecting them as needed, replacing the previous approach of aggregating from local data arrays. (VisorVariableManager.tsx)

Variable Range Application & Synchronization

• Added sendVariableRangeAsync and updated setVariableRangeAsync in VisorFrontend to report range changes to the server and apply them locally, with error handling for failed sends. (VisorFrontend.tsx) [1] [2]
• Simplified and clarified the process of applying variable ranges to scene parts: variable records are set before part updates, and redundant range applications are avoided by checking if the range has changed. (VisorFrontend.tsx, VisorSceneGraph.tsx) [1] [2]

UI Synchronization Enhancements

• Added a refreshSelectionAsync method to the Panel_TopRight_Util class, allowing UI panels to refresh their selection and displayed ranges after variable records are updated. (Panel_TopRight_Util.tsx, Panel_TopRight.tsx) [1] [2] [3]
• Ensured that the UI panel refreshes its selection after new variable records are delivered and the tree view is synchronized. (VisorFrontend.tsx)

Testing and Internal API Adjustments

• Updated tests and internal APIs to use the new variable record delivery and management flow, ensuring that tests reflect the server-delivered variable state. (VisorSceneGraphPartTriggers.test.tsx, VisorSceneGraph.tsx) [1] [2] [3]

Type and Documentation Updates

• Updated type definitions and documentation to reflect the new flow of variable record management and clarify the meaning of fields such as defaultRange. (VisorVariableManager.tsx) [1] [2]

These changes collectively improve consistency, reduce duplication, and make the client more robust to server-driven updates of variable state.