Implement WebSocket-Based Real-Time Chat with Persistent Sessions

# High-Level Overview Checklist for Real-Time Chat with WebSockets

## Backend Setup
- [ ] Set up a WebSocket endpoint for real-time chat (`ws/chat/{session_id}`).
- [ ] Handle incoming and outgoing messages via WebSocket.
- [ ] Maintain a dictionary (or Redis) to store active chat sessions temporarily.

## Session Management
- [ ] Generate a unique `session_id` when a user starts a new chat.
- [ ] Store session details in a persistent database (e.g., user ID, session ID, start time).
- [ ] Implement session expiration logic to clean up inactive sessions.

## Chat History Management
- [ ] Append user queries and AI responses to in-memory storage during the chat session.
- [ ] Save chat history to a database (e.g., MongoDB or PostgreSQL) on WebSocket disconnect.
- [ ] Limit the length of the chat history to manage token size for AI context.

## Resume Chat Sessions
- [ ] Create an API endpoint to fetch past chat history (`GET /session/history?session_id={id}`).
- [ ] Load the chat history into the active session when a user reconnects.

## AI Integration
- [ ] Pass the chat history to the QA agent to provide context for the current query.
- [ ] Stream AI responses back to the user via WebSocket.

## Frontend Integration
- [ ] Establish a WebSocket connection when the user starts a chat.
- [ ] Display real-time AI responses in the chat interface.
- [ ] Fetch past chat history when a user reconnects to a session.

## Optional Enhancements
- [ ] Use Redis for managing active sessions for better scalability.
- [ ] Implement token streaming for real-time AI response generation.
- [ ] Add typing indicators or status updates for improved user experience.