Going to vehicle setup, pwm output page with one client with cockpit open on another causes control input loss in cockpit session

### Bug description

Not tested if this happens with a single client.
If vehicle setup page is open on one client in BlueOS (specifically PWM outputs, 1.4 stable), then motor test function seems to cause cockpit input loss - arm/disarm state does not change.

### Steps to reproduce

Open cockpit on one computer. Open BlueOS on another. Verify control in cockpit (e.g. camera tilt servo.) Open vehicle setup > pwm outputs. Verify control of vehicle lost on first computer - cannot adjust camera tilt, joysticks do not cause motor motion even if system armed. arm/disarm butons have no effect.

### Primary pain point(s)

Check on what a pwm channel is set to, and outputting, lose vehicle control....

### Additional context

_No response_

### Prerequisites

- [x] I have checked to make sure that a similar request has not already been filed or fixed.

Reproduce the issue by opening Cockpit on one computer and BlueOS vehicle setup > PWM outputs on another, then verify camera tilt, joystick, and arm/disarm control. Trace the PWM outputs page and cockpit control-input handling; done means inspecting PWM settings no longer causes the other cockpit session to lose vehicle control.

Written by the indexing model from the issue text.