fix(mobile): stop asking for an API token when the channel list is refused - #9327

The error view sees only the status code, and a 401 can come from a
refused sign-in, a self-hosted relay that refused the key, or a proxy.
Say that the community could not authenticate the request instead of
claiming the sign-in was refused.

Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <[email protected]>

… sign-in ends

When the organization sign-in has ended, the app sends channel reads
unsigned, so the channel list's Retry can never succeed, while the Home
banner already shows "It looks like you're signed out." with a working
Sign in button. The error view now points to that prompt and hides
Retry whenever the organization sign-in prompt is visible for the
current community. Every other failure keeps Retry.

Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <[email protected]>

The ended-sign-in copy and the hidden Retry now apply only when the relay
refuses the read with a 401. Organization relays can serve a read without
the organization sign-in, so a timeout or server error keeps its message and
Retry, as before this PR. The copy points up: the sign-in prompt sits at the
top of Home.

From #9358.

Co-authored-by: Tom Brow <[email protected]>
Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: Logan Johnson <[email protected]>