Implement Daemon Reconnection Retry Logic in Control UI

When the control UI disconnects from the daemon, it never reconnects. We need to implement the state transitions and delays via the iced framework to get the backend to reconnect.

The issue mentions using the iced framework for state transitions and delays. Look for the control UI's connection management code, likely in a module handling daemon communication. Understand the current connection lifecycle and where disconnects are handled. Implement a retry loop with exponential backoff, ensuring it integrates with iced's async/await or event system. Test by simulating a daemon restart.

Scritto dal modello di indicizzazione a partire dal testo della issue.