Add fingerprinting exception for Uphold

[diracdeltas]

Fix brave/brave-browser#4139

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. Go to uphold.com. Make an account and login.
2. Click on the link to verify your identity (as shown in Shield prevents identity verification with webcam when trying to KYC with Uphold brave-browser#4139 (comment))
3. When it asks you to submit ID, allow camera access
4. You should be able to take a picture of your ID

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.

[bsclifton]

rebased so this can re-run CI

[bsclifton]

Followed the steps outlined here - ran into an issue...

• created account 👍
• verified email, etc
• logged in, clicked begin verify
• picked drivers license
• browser asked for camera access 👍 I clicked allow
• my camera light did come on! 🎉
• because I launched via npm run start -- Release the OS then asked me "iTerm is trying to access the camera"
• I clicked "okay" (or whatever it presented). I think it was just an acknowledgement. Does macOS require you to grant access via Accessibility on Mojave? Fresh install on a new machine would likely show the same dialog, but for Brave. I think it's tied to this:

• Uphold camera process timed out at this point- camera light turned itself off
• verification kicked out saying it would be manually reviewed 🙀

At this point, I can't start the process over again ☹️

[corymcdonald]

@bsclifton @diracdeltas Does this PR also address the following?

brave/brave-browser#2993

I've also had experiences where i've been able to get past this but my document actually didn't upload 😭

[diracdeltas]

@corymcdonald yes that's the same issue

[diracdeltas]

if anyone else gets stuck in verification while trying to test this and can't retry, ask in the uphold slack channel for someone to reset your verification state.

[bsclifton]

After Uphold reset the KYC process and I added iTerm (since that's what kicked off the npm run start -- Release) to accessibility (under security and options)... it worked great!

[bsclifton]

(code changes look great too - sorry for the mean mugging; I was actually happy to test this change)