Auto-Switch Wallet View to Last Transaction Network

### What is this about?

When a user processes a transaction from a dapp and returns to the wallet view, the wallet should automatically switch to the network on which the last transaction was made. This ensures that users immediately see the most relevant network context for their recent activity.

### Scenario

- Process a transaction from a dapp on a specific network.
- Navigate back to the wallet view.
- Observe that the wallet remains on the previous network instead of switching to the network used for the transaction.

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

The wallet view should automatically update to the network where the most recent transaction was executed, providing a seamless user experience.

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

No files, tests, or entry points are named. Trace how a dapp transaction completes and how the wallet view selects its active network, then inspect existing tests around those flows. Done means returning to the wallet after a transaction selects the transaction's network and preserves existing behavior otherwise.

Written by the indexing model from the issue text.