ui: "Connecting/Not Connected" status remains visible even after another relay connects successfully”

[mikovskii]

When multiple relays are configured, and at least one relay connects successfully while another relay is blocked(eg Russia) or unreachable, the UI continues to show the Connecting/Not connected status.

This is misleading, because the app is already connected through a working relay, but the interface still suggests that connection is still in progress

Expected behavior:

The “Connecting” status should only be shown while the app is actively trying to establish an initial connection.
If at least one relay has connected successfully, the global “Connecting” indication should disappear, even if another configured relay is still blocked, unreachable, or stuck trying to connect.

Steps to reproduce:

1. Configure two relays
2. Ensure one relay is reachable and connects successfully
3. Ensure the second relay is blocked or unreachable
4. Observe that after the first relay connects successfully, the UI still shows “Connecting”

Screenshots

[link2xt]

We likely want to just display "connected" when at least one relay is connected.

It is a bit of a problem if relay stops working, but users don't notice it and keep advertising it, so everyone sends a copy of message to non-existing server and such messages end up in the server queue. Can easily reach a gigabyte of messages or more stored in the queue if popular relay goes down, but users keep chatting in a group with other relays. Could also be solved on a relay by sending messages to /dev/null (https://serverfault.com/questions/891930/silently-drop-emails-to-specific-invalid-domain-in-postfix), but this will require operators to notice and the server may go back online later.

If we change connectivity status for the case when some relays don't work, we probably need to also stop advertising relays for which there has been no IMAP connection for a long time.