teleop/quest: run uvicorn on module._loop, remove WS cross-loop bridge

Problem

QuestTeleopModule runs uvicorn in its own daemon thread (separate asyncio loop), while the camera handlers run on module._loop. Sending JPEG frames to connected WebSocket clients therefore goes through a thread bridge: a _ws_loop reference captured inside the /ws handler, used by a module-level _push_jpeg helper via asyncio.run_coroutine_threadsafe. This works but is convoluted

Refactor req

Move uvicorn onto module._loop so the WebSocket and handle_color_image execute on the same loop, then the push becomes a direct await ws.send_bytes(jpeg)

Synced from DIM-969 by summer

Start by locating QuestTeleopModule and its module._loop, then inspect the /ws handler, _ws_loop reference, _push_jpeg helper, and handle_color_image. The refactor is done when uvicorn runs on module._loop, WebSocket handling and image processing share that loop, and JPEG delivery uses a direct await ws.send_bytes(jpeg).