[Frontend] Add audit-friendly wallet action confirmation receipts

## Problem
After a wallet transaction, users need a durable explanation of what was requested, what was signed, and what the network confirmed.
## Acceptance criteria
- Receipts distinguish intent, submitted operation, final status, and explorer link.
- Sensitive signing material is never persisted or displayed.
- Receipt data survives refresh and handles failed/unknown transactions.
- Tests cover successful, rejected, replaced, and partial multi-operation flows.

Start by tracing the existing wallet transaction flow and how transaction data is persisted across refreshes. Define receipt boundaries for intent, submitted operation, final status, and explorer link while excluding signing material. Done means successful, rejected, replaced, unknown, and partial multi-operation flows are persisted and covered by tests.

Written by the indexing model from the issue text.