Implement WebSocket Route to Publish Sensor Readings

[FelizCoder]

Description: As part of the CrewStand project, to enhance real-time monitoring capabilities, we need to implement a WebSocket route on the backend. This route will publish each sensor reading as soon as it is received, allowing clients to subscribe and receive updates in real-time.

Requirements:

1. WebSocket Endpoint:

   • Implement a WebSocket endpoint (e.g., /ws/sensors) that clients can connect to in order to receive real-time sensor readings.

2. Publish Sensor Readings:

   • Ensure that each sensor reading received by the /v1/sensors/flowmeters/{id}/reading endpoint is published to all connected WebSocket clients.
   • The data published should conform to the SensorReading schema.

3. Client Management:

   • Manage client connections, ensuring that new clients can connect and subscribe to sensor updates.
   • Handle client disconnections gracefully, ensuring server stability.

4. Error Handling:

   • Implement robust error handling, ensuring any issues with client connections or data publishing are handled gracefully.
   • Ensure server logs provide meaningful information for any errors encountered.

5. Testing:

   • Write unit and integration tests to ensure the WebSocket route works correctly.
   • Test client connections, data publishing, and disconnections to ensure robustness.

Example WebSocket Message: The messages sent over the WebSocket should follow the SensorReading schema:

{
  "value": 0.42,
  "timestamp_ns": 1730906908814683100
}

Acceptance Criteria:

• The WebSocket endpoint correctly publishes sensor readings in real-time.
• Clients can connect, receive updates, and handle disconnections properly.
• Tests are written and pass successfully.
• Documentation is updated to reflect the new WebSocket route.

---

Additional Information:

• Refer to the current implementation of the sensor readings endpoint.
• Utilize the SensorReading schema as described

[FelizCoder]

followup #43