Exit retry-loop when user tries linking their wallet with a different Uphold account.

[szilardszaloki]

Resolves brave/brave-browser#17271, resolves brave/brave-browser#17265.

• adding the mismatched provider accounts notification
  
• kicking back the wallet to NOT_CONNECTED
• adjusting unit tests

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:

[bsclifton]

Nice work on this! This is a great fix 😄

[LaurenWags]

Verified with

Brave | 1.30.14 Chromium: 92.0.4515.131 (Official Build) nightly (x86_64)
-- | --
Revision | 6b8d6c56ce21e38a72f7c4becb5abc1fa5134f29-refs/branch-heads/4515@{#1933}
OS | macOS Version 10.15.7 (Build 19H1323)

Scenario 1: Clean profile

1. Clean install 1.30.14, staging env
2. Enable Rewards, link KYC'd Uphold wallet
3. Manually disconnect from Uphold (from wallet panel)
4. Confirm you are returned to pre-link state (UI, no balance, etc)
5. Link a second (different) KYC'd Uphold wallet
6. Confirm logs show 403 error like below once (not continuously):

[ RESPONSE - OnRequest ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/5...............6/claim
> Result: Failure
> HTTP Code: 403
> Body: {"message":"error linking wallet: unable to link wallets: unable to match wallets: wallets do not match","code":403}

7. Confirm UI does not show "Wallet verified" or a balance
8. Confirm notification requested in Show error notification when user tries to connect second custodian account in wallet generation flow brave-browser#17271 is shown:

9. "Learn more" button links to https://support.brave.com/hc/en-us/articles/360034841711-What-is-a-verified-wallet-
10. Confirm "x" closes the notification
11. Confirmed wallet was sent back to NOT_CONNECTED

Example	Example

TBD:
Scenario 2: Upgrade profile

1. Using current release version, 1.27.111, clean profile, staging env, enable Rewards, link KYC'd Uphold wallet
2. Manually disconnect from Uphold (from wallet panel)
3. Confirm you are returned to pre-link state (UI, no balance, etc)
4. Link a second (different) KYC'd Uphold wallet
5. Confirm UI appears fine (UI, balance is shown), and logs show 403 error for linking as expected.
6. Close browser
7. "Upgrade" (rename profile to Brave-Browser-Nightly) to 1.30.x
8. Confirm logs show 403 error once (not continuously)

[ RESPONSE - OnRequest ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/1...........8/claim
> Result: Failure
> HTTP Code: 403
> Body: {"message":"error linking wallet: unable to link wallets: unable to match wallets: wallets do not match","code":403}

9. Open panel and confirm notification requested in Show error notification when user tries to connect second custodian account in wallet generation flow brave-browser#17271 is shown

10. "Learn more" button links to https://support.brave.com/hc/en-us/articles/360034841711-What-is-a-verified-wallet-
11. Confirm "x" closes the notification
12. Confirmed wallet was sent back to NOT_CONNECTED

Example	Example