Proxy requests for CRLSets through crlsets[n].brave.com

[jumde]

Test Plan

1. Open Brave Browser with a fresh profile
2. Navigate to brave://components (wait for a few mins) and verify that CRLSets is updated. It should have a non-zero version number.
3. Verify that no requests are sent to:

www.google.com/dl/release2/chrome_component/*crl-set*
*.gvt1.com/edgedl/release2/chrome_component/*crl-set*
*://dl.google.com/release2/chrome_component/*crl-set*

[jumde]

Reverted: brave/brave-core#986 (master and 0.58.x)

[diracdeltas]

also need to proxy the update.googleapis.com request from #2280

[bbondy]

Had to be reverted, follow logic here:
brave/brave-core#997 (comment)

[LaurenWags]

Verified passed with

Brave	0.64.72 Chromium: 74.0.3729.131 (Official Build) beta(64-bit)
Revision	518a41c1fa7ce1c8bb5e22346e82e42b4d76a96f-refs/branch-heads/3729@{#954}
OS	Mac OS X

• Verified test plan from Enabling CRLSets; Capping the maximum component updates per request to go-updater to 1 brave-core#1581
• Verified test plan from description: no connections to sites listed in description and CRLSet has non-zero version number:
  
  

Verification passed on

Brave	0.64.72 Chromium: 74.0.3729.131 (Official Build) beta(64-bit)
Revision	518a41c1fa7ce1c8bb5e22346e82e42b4d76a96f-refs/branch-heads/3729@{#954}
OS	Windows 10 OS Build 17134.523

• Verified test plan from Enabling CRLSets; Capping the maximum component updates per request to go-updater to 1 brave-core#1581
• Verified test plan from description

Verification passed on

Brave	0.64.74 Chromium: 74.0.3729.131 (Official Build) beta(64-bit)
Revision	518a41c1fa7ce1c8bb5e22346e82e42b4d76a96f-refs/branch-heads/3729@{#954}
OS	Linux

• Verified on clean profile, components had non-zero values
• Verified no connections were made to Google servers
• Verified Brave components showed both state Component not update and Up-to-date