Disable Wayback Machine for ".onion" addresses

[DanielKim1]

Resolves brave/brave-browser#9342

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-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-issues-with-tracking-protection
  • https://github.com/brave/brave-browser/wiki/QA-Guide

Test Plan:

1. Open a new private window with Tor (Use the hamburger menu on the top right corner of the Brave window, or press option + command + N)
2. Go to the 404 page for the New York Times (http://www.nytimes3xbfgragh.onion/404)
3. Check that the "Sorry, that page is missing" banner does not appear
   NYT onion URL source: https://open.nytimes.com/https-open-nytimes-com-the-new-york-times-as-a-tor-onion-service-e0d0b67b7482

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.

[simonhong]

@DanielKim1 Welcome and thanks for contributing to Brave project :)
I don't know much about Tor. I'll pass review request to Tor/Security export (@fmarier @darkdh ).

[DanielKim1]

Thanks Simon! I'm a big fan of this project :)

[darkdh]

lgtm, also request review from @riastradh-brave

[diracdeltas]

@riastradh-brave is not actively working on tor anymore, but this lgtm

[simonhong]

Hmm, how we make this PR run in CI builder?

[simonhong]

@DanielKim1 #5312 is created to run this PR from CI.
We can merge this if CI is happy. :) Let's wait.

[simonhong]

CI only failed with unrelated flaky test. So you can merge this @DanielKim1 🎉
I'm looking forward to see your contribution again 👍

[DanielKim1]

Thanks Simon!
Unfortunately, it looks like I can't merge this PR:

Only those with write access to this repository can merge pull requests.

Could someone else merge this PR in, please? 🙏