Replace crlsets with redirector

[linhkikuchi]

Resolves brave/brave-browser#20609
For https://github.com/brave/devops/issues/3313

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• 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, npm run lint, 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:

Use Proxyman (MacOS) or mitmproxy, run the browser with fresh profile using the proxy ( e.g. --proxy-server="localhost:9090"), verify:

• spellcheck dict request is 200 https://dict.brave.com/edgedl/chrome/dict/en-gb-9-0.bdic (the old request was https://crlsets.brave.com/edgedl/chrome/dict/en-gb-9-0.bdic)
• all other /edgedl/release2/chrome_component/, /release2/chrome_component/, /dl/release2/chrome_component, /update-delta/hfnkpimlhhgieaddgfemjhofmfblmnib/, /edgedl/chromewebstore/, /edgedl/release2/, /update-delta/ggkkehgbnfjpeggfpleeakpidbkibbmn/ requests are now using https://redirector.brave.com and all return 200
• other componentupdate requests should return 200 as well
• go to brave://components and able to update CRLSet

[iefremov]

Will need to update
https://github.com/brave/devops/wiki/Mappings-for-proxied-URLs
https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)#services-we-proxy-through-brave-servers

[linhkikuchi]

Will need to update https://github.com/brave/devops/wiki/Mappings-for-proxied-URLs https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)#services-we-proxy-through-brave-servers

Updated