🐛 Describe the bug

Issue Description

Current Behavior

Currently, when a user loses connection to a LiveKit room (due to network issues or other disruptions), the application does not attempt to automatically reconnect. This results in a poor user experience as users need to manually rejoin the room or restart the application.

Problem Impact

• Users are disconnected from rooms without recovery options
• Manual intervention required to rejoin rooms
• Poor user experience in unstable network conditions
• No feedback to users about connection status

Proposed Solution

Implement an automatic reconnection mechanism that:

• Attempts to reconnect automatically when connection is lost
• Provides user feedback during reconnection attempts
• Gracefully handles failed reconnection scenarios

Technical Requirements

1. Maximum of 3 reconnection attempts
2. 2-second delay between attempts
3. User notifications for connection status
4. Proper cleanup of connection attempts when leaving room
5. Connection state tracking using GetX observables

Acceptance Criteria

• Application automatically attempts to reconnect when connection is lost
• Users receive visual feedback about connection status
• Reconnection attempts stop after maximum tries or successful connection
• All resources are properly cleaned up on room exit
• Connection state is properly tracked and observable
• Code is properly tested and documented