Sanitized wayback url from wayback machine

[simonhong]

Resolves brave/brave-browser#32395

Only allow to load valid wayback url that has http/https scheme and valid wayback domain.

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run lint, npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

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, 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-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

WaybackMachineURLFetcherUnitTest.WaybackURLSanitizeTest

See the linked issue for manual test.

[kjozwiak]

Verification PASSED on Win 11 x64 using the following build(s):

Brave | 1.59.56 Chromium: 116.0.5845.114 (Official Build) nightly (64-bit)
-- | --
Revision | 11676eb8c4bf058787c740d5fd2d089971f5d942
OS | Windows 11 Version 22H2 (Build 22621.2215)

Using the STR/Cases outlined via brave/brave-browser#32395 (comment), ensured that Sorry, there is no saved version available. was being displayed when visiting https://brave.com/bo/ and clicking on Check for saved versions via the Wayback Machine as per the following:

• using Fiddler, created a new rule to change the JSON response for https://brave-api.archive.org/wayback/available?url=https://brave.com/bo/ to the JSON that's mentioned via [hackerone] validate wayback URL before navigating brave-browser#32395 (comment)
• enabled the Fiddler rule and visited https://brave.com/bo/
• ensured that clicking Check for saved versions displayed Sorry, there is no saved version available. via the banner

Example	Example	Example	Example