fix: SuccessTx and ErrorTx link to the explorer of the network the transaction was sent on (closes #622)

SuccessTx and ErrorTx built their recipient, block, hash and decoded-action
address links for the active network. After a network switch, WaitTx now finds
a transaction on the network it was sent on and moves on to these screens, whose
links then opened an explorer where the transaction does not exist. Both
screens now keep the transaction's chain id with their view data and build
every link for that network, as WaitTx does. A stored SuccessTx or ErrorTx
whose chain id names no network is refused on restore, as a stored transaction
already is.

Model: opus-5-5

README.md

@@ -1922,9 +1922,12 @@ view would leave a wallet one click from deletion.
     - Amount + symbol
     - To: color dot + full address + etherscan link, or for a contract creation
       the same sentence as on WaitTx
-    - Block number
+    - Block number + etherscan link
     - Transaction hash: full hash (tap to copy) + etherscan link
     - "Done" button
+- **Behavior**: As on WaitTx, every etherscan link on the screen opens the
+  explorer of the network the transaction was sent on, whichever network is
+  active.
 - **Transitions**:
     - "Done" in the approval popup → closes the popup window
     - "Done" otherwise → resets the navigation stack, then → **AddressToken**
@@ -1944,6 +1947,9 @@ view would leave a wallet one click from deletion.
     - Transaction hash section (hidden if broadcast failed before getting hash):
       full hash (tap to copy) + etherscan link
     - "Done" button
+- **Behavior**: As on WaitTx, every etherscan link on the screen opens the
+  explorer of the network the transaction was sent on, whichever network is
+  active.
 - **Transitions**:
     - "Done" in the approval popup → closes the popup window
     - "Done" otherwise → resets the navigation stack, then → **AddressToken**