Converting ExternalWalletLinkingFailedNotification notifications into modals.

[szilardszaloki]

Resolves brave/brave-browser#16652 (resolves brave/brave-browser#13997, resolves brave/brave-browser#16650).

• uphold_bat_not_allowed_for_user ==> upholdBATNotAllowedModal
• uphold_blocked_user ==> upholdBlockedUserModal
• uphold_pending_user ==> upholdPendingUserModal
• uphold_restricted_user ==> upholdRestrictedUserModal
• wallet_device_limit_reached ==> deviceLimitReachedModal
• wallet_mismatched_provider_accounts ==> mismatchedProviderAccountsModal
• fixing the upholdBATNotAllowedModal modal

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
• 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, npm run lint, 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:

There are 7 modals altogether that need to be tested:

• Provider-agnostic:
  • deviceLimitReachedModal (Learn More goes here):
    
    Try reaching the device limit.
  • kycRequiredModal (No Learn More links) – Uphold example:
    
    Try verifying your Rewards wallet with a non-KYC'd wallet provider account.
  • mismatchedProviderAccountsModal (Learn More goes here) – Uphold example:
    
    Verify your Rewards wallet with a wallet provider, manually disconnect, then try verifying your Rewards wallet with a different account from the same provider.
• Uphold-specific (here is how you can repro the use-cases for the below modals):
  • upholdBATNotAllowedModal (Learn More goes here):
    
  • upholdBlockedUserModal (Learn More goes here):
    
  • upholdPendingUserModal (Learn More goes here):
    
  • upholdRestrictedUserModal (Learn More goes here):
    

Make sure you don't see the corresponding notifications that we showed previously.

[zenparsing]

Looks good to me. I know SonarCloud is complaining, but I don't necessarily see a problem.

[szilardszaloki]

SonarCloud is reporting duplicated lines due to how we currently structure code in settingsPage.tsx.