Build a Scalable WebSocket Server with Room Management

Build a production-ready WebSocket server in [PROGRAMMING_LANGUAGE] using the [WEBSOCKET_LIBRARY] library. The server will power a [APPLICATION_TYPE] application (e.g., real-time chat, live dashboard, collaborative editor) and must handle up to [EXPECTED_CONCURRENT_USERS] concurrent connections. Please implement the following features with clean, well-documented code: 1. **Server Setup & Configuration**: Initialize the WebSocket server on port [PORT] with configurable options for heartbeat/ping-pong intervals (default 30 seconds), maximum payload size, and CORS settings for allowed origins [ALLOWED_ORIGINS]. 2. **Connection Lifecycle Management**: - Handle new connections with an authentication step that validates a [AUTH_METHOD] (e.g., JWT token, API key) passed during the handshake. - Assign each connection a unique client ID and store metadata (user ID, connected timestamp, rooms). - Implement graceful disconnection handling with cleanup of all subscriptions and rooms. - Add automatic reconnection detection using client fingerprinting. 3. **Room/Channel System**: - Allow clients to join and leave named rooms with optional capacity limits. - Support broadcasting messages to all clients in a specific room. - Implement room-level permissions (read-only, read-write, admin). - Provide a mechanism to list active rooms and their member counts. 4. **Message Protocol**: Define a structured JSON message protocol with the following message types: `join_room`, `leave_room`, `broadcast`, `direct_message`, `presence_update`, and `error`. Each message should include a type field, a unique message ID, a timestamp, and a payload object. 5. **Error Handling & Resilience**: Implement structured error codes and messages, handle malformed messages gracefully, add connection timeout handling, and include try-catch blocks with logging for all critical paths. 6. **Monitoring & Logging**: Add an endpoint or admin command to retrieve server stats (active connections, rooms, messages per second), and integrate structured logging with [LOGGING_PREFERENCE]. Include a sample client-side connection snippet and a brief explanation of how to horizontally scale this server using [SCALING_STRATEGY] (e.g., Redis pub/sub, sticky sessions).