Fix/issue 470 stuck reconnecting (#495)

* fix(ws): stop chat opening from racing the singleton into a stuck RECONNECTING

Root cause: HermesWsClient is a global singleton connected once at login;
every tab observes its single connectionStatus. ChatViewModel is recreated
on every chat-tab open and its init calls connectWebSocket() -> wsClient.connect().

connect() only guarded the CONNECTED case, so when the socket had dropped
(singleton in RECONNECTING with its own scheduled reconnect) opening chat
spawned a SECOND socket on the same webSocket field. The orphaned socket's
later onClosed set connected=false + re-armed RECONNECTING after the new
socket connected, and currentBackoff kept resetting on each chat open,
leaving the status stuck on RECONNECTING while every other tab (which never
calls connect()) stayed healthy.

Fix:
- HermesWsClient.connect() now no-ops while CONNECTING/RECONNECTING (in-flight
  socket already pending) and while AUTH_EXPIRED (needs re-auth, not a loop).
- ChatViewModel.connectWebSocket() mirrors the same terminal-state guard so
  the chat tab never disturbs an already-working or already-recovering
  connection. Behavior-preserving: happy path (CONNECTED) and genuine
  terminal states (DISCONNECTED/NO_NETWORK) still connect as before.

* fix(#470): sync cookie store scope with selected profile ID

Update AuthManager to switch CookieManager to the active server profile ID on startup and on runtime profile change.

* fix(#470): prevent stale token cache and load initial cookie scope

Pass active profile scope to CookieManager.initialize on startup and update setProfileToken to sync the in-memory cachedToken.

* feat(chat): add re-login action and credentials popup to connection banner

Add a Re-login button to the connection status banner and a dialog to prompt for credentials, allowing the user to refresh session cookies/tokens and reconnect the WebSocket.

* fix(chat): address PR #495 review feedback

* fix(chat): restore reconnect action in banner

* fix: resolve composable invocation in ReloginDialog

* fix(chat): enable re-login action during reconnecting state

Add the Re-login button to the connection status banner when connectionStatus is RECONNECTING, allowing users to re-authenticate and resolve stuck reconnect loops.

app/src/main/java/com/m57/hermescontrol/data/ws/HermesWsClient.kt

@@ -165,6 +165,25 @@ object HermesWsClient {
             Log.d(TAG, "Already connected — skipping")
             return
         }
+        // Guard against re-entrant connect() while a connection is already in
+        // flight. The singleton may be CONNECTING (mid handshake) or RECONNECTING
+        // (a scheduled reconnect is pending). Opening a second socket on the same
+        // `webSocket` field races the in-flight one and can leave the status
+        // stuck on RECONNECTING (e.g. the chat tab calls connect() on every open
+        // while the app-level reconnect is already running). Only start a fresh
+        // socket from a terminal state.
+        if (_connectionStatus.value == ConnectionStatus.CONNECTING ||
+            _connectionStatus.value == ConnectionStatus.RECONNECTING
+        ) {
+            Log.d(TAG, "Connection already in flight (${_connectionStatus.value}) — skipping")
+            return
+        }
+        // AUTH_EXPIRED cannot be resolved by reconnecting alone — caller must
+        // re-authenticate. Leave the status as-is so the UI can surface sign-in.
+        if (_connectionStatus.value == ConnectionStatus.AUTH_EXPIRED) {
+            Log.d(TAG, "Connection is AUTH_EXPIRED — skipping reconnect; re-auth required")
+            return
+        }
         intentionalClose.set(false)
         currentBackoff = INITIAL_BACKOFF_MS
         _connectionStatus.value = ConnectionStatus.CONNECTING