[Remote rendering 4.5] Remote camera interaction end-to-end

### 📝 Description of the feature

Make rotate, pan, and zoom work against the server-side interactor: the client forwards the interaction event, the server applies it to the camera, renders, and streams the updated frame back. The stock interaction adapter doesn't reliably handle the event format the canvas emits, so a direct dispatch stands in.

Note:

In the spike, the stock vtkRemoteInteractionAdapter.ProcessEvent didn't recognize the JSON event format RemoteCanvas emits, because RemoteCanvas was emitting different event shapes (e.g. both flat {x, y} and nested {position: {x, y}} shapes.
A workaround was used in the spike, dispatching events directly to an interactor instead of going through the adapter, since it wasn't clear whether the adapter's strict behavior is intended or an upstream issue whose fix is to accept both shapes.
If a similar issue is encountered in the course of this user story, we could first check with Kitware on whether we resolve the issue by conforming RemoteCanvas to a single shape or whether the fix is on the adapter side (if it's not intended to be as strict)

### Acceptance Criteria

Rotate, pan, and zoom work in remote mode.

### 💵 Business Value

_No response_

### 🔗 Useful links and references

_No response_

Inizia tracciando l’emissione degli eventi di RemoteCanvas e il percorso dell’interactor lato server, quindi esamina vtkRemoteInteractionAdapter.ProcessEvent e le diverse strutture degli eventi JSON descritte qui. Conferma il formato dell’evento previsto o l’approccio di dispatch diretto; il lavoro è completato quando rotazione, pan e zoom funzionano in modalità remota e i frame aggiornati vengono trasmessi nuovamente.

Scritto dal modello di indicizzazione a partire dal testo della issue.