fix(remote-ws): route by the connection's device_id, not the payload's master
Commands from the miniplayer weren't reaching the player: play/pause STATE synced (track/status frames display regardless of id), but the transport commands went nowhere. Cause: device_message tagged broadcasts with the client-reported `device_id` from the payload. An old CLI (pre-0.7.1) clobbers its own id from a device_registered broadcast, so its tracks were tagged with the WEB's id; the miniplayer then targeted commands at that id and the server routed them back to the web (which ignores them), never to the CLI. Fix: use the connection's registered device_id (assigned at register, authoritative) for caching, primary, and the broadcast tag — ignore the payload id entirely. Robust regardless of client version.