Swap page available for locked wallet

[vadimstruts]

Fixed wallet lock detection when brave://wallet/* pages opening

Resolves brave/brave-browser#31236

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run lint, npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

Preconditions:

• initialized wallet

Steps:

1. Unlock wallet
2. Go to swap page
3. Close the browser by clicking "Exit"
4. Open browser
5. Swap page is not available, i.e. there is no any wallet information displayed
6. Unlock wallet
7. Go to swap page (by clicking the swap button)
8. Swap page opened, all related information displayed

[ShivanKaul]

Why do we need to reload here? Is it because on re-opening the app we want to make sure we have the current lock state?

[vadimstruts]

It is for situation when you tried to open browser tab with address brave://wallet/swap and got empty page
but then you unlocked the wallet and pressed the swap button.
without refresh, you will see the same empty tab brave://wallet/swap
But if you refresh it, all the info will be displayed

[SergeyZhukovsky]

++