Add referer exception for geetest captchas

[diracdeltas]

The captcha fails unless referer is allowed

fix brave/brave-browser#1740

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
  • Windows
  • macOS
  • Linux
• Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
  • Windows
  • macOS
  • Linux
• 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

Test Plan:

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

[diracdeltas]

went thru manual test plan and verified unit tests on macOS

[pes10k]

looks good to me 👍

[bbondy]

Nice! Thanks for fixing this, I've been meaning to.

[bbondy]

master: a57dc16
0.57.x: aea4680
0.56.x: 7e4a261
0.55.x: 10f0dd0

[kevinsimper]

How is this scalable adding domains manually? Especially when it is not transparent to users that there is a white-list where tracking can happen?

[aabedraba]

Bumping up @kevinsimper questions.
@pes10k any input on this?

[pes10k]

Yep, our current system def doesn't scale, for all the reasons said above. The solution going forward (expect implementation to begin this week) is going to be this: brave/brave-browser#8696