Exempt password managers from the Uphold content script restrictions

[fmarier]

This should mitigate some of the bad UX described in brave/brave-browser#6309.

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Android
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that these changes pass automated tests (unit, browser, security tests) on
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that all lint errors/warnings are resolved (npm run lint)
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone
• Public documentation has been updated as necessary. 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-Protection-Mode
  • 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-issues-with-tracking-protection
  • https://github.com/brave/brave-browser/wiki/QA-Guide

Test Plan:

1. Install the 1 Password X extension.
2. Go into brave://rewards and start verifying the wallet with Uphold.
3. On the Uphold account creation / login page, click on the 1Password icon.

If the icon is working (as opposed to being disabled and contained within a circle), then this change is working.

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

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.

[szaimen]

@fmarier I would like to see Enpass and SafeInCloud beeing included here. (These are good password managers that aren't based on subscriptions)
Thank you for your work!
Please pink me if you need links to their websites or chrome webstore extensions.

[fmarier]

@szaimen Are you talking about these ones?

• Enpass (extension)
• SafeInCloud (extension)

[szaimen]

Are you talking about these ones?

• Enpass (extension)
• SafeInCloud (extension)

@fmarier Yes 👍

[fmarier]

Not sure why CI is not showing up as green, but I have one run which passed except for Android:
https://staging.ci.brave.com/job/brave-browser-build-pr/job/francois-whitelist-password-managers-6309/3/

and a rebuild just on Android which also passed:
https://staging.ci.brave.com/job/brave-browser-build-pr/job/francois-whitelist-password-managers-6309/6/