Issue 5800: Add a fingerprint exception for sandbox.uphold.com

[jumde]

Fix brave/brave-browser#5800

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. Navigate to https://sandbox.uphold.com
2. Create an account and initiate verification.
3. Enter your address > Next > Upload Driver's license
4. Upload your driver's license.
5. Navigate to brave shields and verify that no fingerprinting requests are blocked (Cross Site Device Recognition blocked)

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.

[diracdeltas]

lgtm assuming tests pass!

[bsclifton]

LGTM! 😄👍

[LaurenWags]

The following tests were done using 0.71.44 on Nightly (macOS):

1. Launched clean profile with 0.71.44 with staging parameter. Enabled Rewards, followed 'verify wallet' prompts to get to sandbox Uphold site. Created a fake profile. Verified I was able to submit documents for KYC without issue.
2. Launched clean profile with 0.71.44. Enabled Rewards, followed 'verify wallet' prompts to get to prod Uphold site. Created a fake profile. Verified I was able to submit documents for KYC without issue.
3. Launched clean profile with 0.68.132 with staging parameter. Enabled Rewards. Navigated to sandbox Uphold site. Created a fake profile. Verified I was unable to submit documents for KYC (FP on default shields is stopping me). Renamed profile to Nightly and launched with 0.71.44. Verified I was now able to submit documents for KYC without issue.
4. Launched clean profile with 0.68.132. Enabled Rewards. Navigated to prod Uphold site. Created a fake profile. Verified I was unable to submit documents for KYC (FP on default shields is stopping me). Renamed profile to Nightly and launched with 0.71.44. Verified I was now able to submit documents for KYC without issue.

In all cases above I wasn't going for actual KYC so I didn't use real docs, but using 0.71.44 I did not encounter any FP issues which prevented me from uploading photos. I did encounter the autoplay issue @jumde found only once on 0.71.44 and was unable to reproduce again.

[pj]

Hi guys, wrong @pj! 😂

[LaurenWags]

ack, sorry (wrong) @pj - thought I removed that. apologies!