[Feature] Add a manual retry button after reconnect attempts are exhausted

Problem

When Codex loses network connectivity while sending a request, it automatically retries until the retry limit is reached. The UI then remains in a failed/reconnecting state (for example, Reconnecting... waiting for network, Переподключение 5/5) and shows the request error.

Suggestion

Add an explicit Continue / Retry connection action in this state that starts a new connection attempt.

The action should:

• reset the exhausted retry counter and backoff;
• retry the connection/request without losing the current conversation or draft;
• show clear progress and a useful error if the manual attempt fails again;
• remain available after automatic retries have been exhausted.

Context

Observed in the Codex desktop app after a request failed with an HTTP 403 response from backend-api/codex/responses. A manual retry would let the user recover without restarting the task or waiting for another automatic cycle.

Start by tracing the Codex UI state that displays the exhausted reconnect counter and the automatic retry/backoff handling. Add a manual Continue or Retry connection action that preserves the conversation or draft, resets retry state, reports progress and errors, and remains available after automatic retries end.