🟡 MEDIUM: Modularize RemoteCameraStreamer (994 lines)

## Problem

`RemoteCameraStreamer.swift` is **994 lines** handling multiple unrelated concerns.

## Mixed Concerns

1. **Bonjour/mDNS discovery** - Finding camera servers
2. **Network connection management** - TCP/WebSocket handling
3. **Video encoding** - Compression and format conversion
4. **UI state management** - Connection status, errors
5. **Protocol handling** - Custom streaming protocol

## Proposed Decomposition

```
Remote Camera Feature
├── CameraServerDiscovery (~200 lines)
│ └── Bonjour browsing, service resolution
├── RemoteCameraConnection (~250 lines)
│ └── Connection lifecycle, reconnection
├── CameraStreamEncoder (~250 lines)
│ └── Video encoding, compression
├── CameraStreamProtocol (~150 lines)
│ └── Message framing, serialization
└── RemoteCameraViewModel (~150 lines)
└── UI state only
```

## Acceptance Criteria

- [ ] Each component has single responsibility
- [ ] Discovery can be reused for other services
- [ ] Connection handling is testable
- [ ] Encoder can be unit tested with sample frames

Start by reading RemoteCameraStreamer.swift and map its Bonjour/mDNS discovery, connection, encoding, protocol, and UI state responsibilities. Use the proposed component boundaries as a decomposition plan; done means each component has one responsibility, discovery is reusable, connection handling is testable, and the encoder can be unit tested with sample frames.

Written by the indexing model from the issue text.