fix: the confirmation screen reads its balance on the network it is drawn for (closes #558)

ConfirmTx showed and checked the balance Send handed it, so a popup reopened onto a confirmation saved before a network switch stated the other network's balance and checked the amount against it.

Each time it is shown, ConfirmTx now reads the From address's ETH balance, and for a token send its token balance at the scale the amount is shown with, from the node of the network it is drawn for. Until the read returns the balance line says "Loading..." and Sign & Send stays disabled; a read that fails is stated as unknown and blocks the send. The fee estimate starts once the read is done, since a max ETH send's amount comes from the balance. Send no longer hands balances over.

Model: opus-5-5

README.md

@@ -1719,32 +1719,39 @@ view would leave a wallet one click from deletion.
       the reserve the transaction does not use. If the balance no longer covers
       the fee, the amount is left as it was and the amount-plus-fee error below
       blocks the send
-    - Your balance: value + symbol (USD in parentheses), or `unknown (SYMBOL)`
-      for a token whose scale is unknown
+    - Your balance: the From address's balance on the network the screen is
+      drawn for, read from that network's RPC endpoint each time the screen is
+      shown, so a screen the popup reopens onto after the network was switched
+      states and checks the balance on the new network. "Loading..." until the
+      read returns, then value + symbol (USD in parentheses), or
+      `unknown (SYMBOL)` for a token whose scale is unknown or when the read
+      failed. The amount check uses the same balances: the ETH balance, and for
+      a token transfer the token balance as well
     - Network fee: "Estimating..." then two lines, or "Unable to estimate",
-      fetched async. The first line is what the transfer is expected to cost,
-      `gasLimit * gasPrice` (USD in parentheses); the second is the
-      `gasLimit * maxFeePerGas` reserve the node requires, which is what the
-      balance check gates on. The second line is omitted on a network with no
-      type-2 pricing, where the two are the same number, but its space is
-      reserved either way
+      fetched async once the balance is read. The first line is what the
+      transfer is expected to cost, `gasLimit * gasPrice` (USD in parentheses);
+      the second is the `gasLimit * maxFeePerGas` reserve the node requires,
+      which is what the balance check gates on. The second line is omitted on a
+      network with no type-2 pricing, where the two are the same number, but its
+      space is reserved either way
     - Warnings: inline warnings from the local checks (scam address, self-send)
       plus four reserved warning boxes made visible by the async checks —
       recipient with no transaction history, recipient is a contract, burn
       address, and an Etherscan phishing/scam label
-    - Errors (insufficient balance), plus three reserved error boxes — the
-      amount plus the fee exceeds the balance (ETH transfers), not enough ETH to
-      pay the fee for the transfer (ERC-20 transfers), and the fee could not be
-      estimated. The first two are mutually exclusive per transfer type, so only
-      the applicable one holds space. The last names its cause: for a token
-      whose scale is unknown the fee can never be estimated, and it says the
-      wallet does not know how many decimal places the token uses and that the
-      transaction cannot be sent; for any other failure it asks the user to go
-      back and try again
+    - Errors (insufficient balance, or a balance that could not be read, which
+      asks the user to go back and try again), plus three reserved error boxes —
+      the amount plus the fee exceeds the balance (ETH transfers), not enough
+      ETH to pay the fee for the transfer (ERC-20 transfers), and the fee could
+      not be estimated. The first two are mutually exclusive per transfer type,
+      so only the applicable one holds space. The last names its cause: for a
+      token whose scale is unknown the fee can never be estimated, and it says
+      the wallet does not know how many decimal places the token uses and that
+      the transaction cannot be sent; for any other failure it asks the user to
+      go back and try again
     - Password: an inline field on this screen, not a modal, with its own error
       line
-    - "Sign & Send" button (disabled if errors, and while the network fee
-      estimate is pending or unavailable)
+    - "Sign & Send" button (disabled if errors, while the balance is being read,
+      and while the network fee estimate is pending or unavailable)
 - **Transitions**:
     - "Sign & Send" (correct password) → broadcast tx → **WaitTx**
     - "Sign & Send" (correct password) → broadcast fails → **ErrorTx**