Adds back certain UA client hints.

[szilardszaloki]

• Sec-CH-UA-Arch: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-CH-UA-Arch
• Sec-CH-UA-Bitness: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-CH-UA-Bitness
• Sec-CH-UA-Full-Version-List: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-CH-UA-Full-Version-List
• Sec-CH-UA-WoW64: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-CH-UA-WoW64

Resolves brave/brave-browser#25694
Security review: https://github.com/brave/reviews/issues/1696

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

Test Plan:

Load YouTube live streams that have the chat enabled (e.g. https://www.youtube.com/watch?v=_uMuuHk_KkQ) multiple times, and make sure the https://www.youtube.com/live_chat?continuation=... requests never hang (i.e. live chat loads right away/together with the video/page — and not with a 20-sec delay). The 20-sec delay can easily be reprod on any channel/any version at the moment.

[bsclifton]

Fix works great! Will defer the implementation details to @ShivanKaul 😄

[ShivanKaul]

Just a note that we will be clamping to the major version for Sec-CH-UA-Full-Version-List like we did for the JS equivalent in #16177

[mkarolin]

LGTM

[kjozwiak]

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

Brave | 1.70.51 Chromium: 127.0.6533.88 (Official Build) nightly (64-bit)
-- | --
Revision | c39ff5a89233f396d214b305233de91ff13a8b9e
OS | Windows 11 Version 23H2 (Build 22631.3958)

Using 1.70.22 Chromium: 127.0.6533.73 and the STR/Cases outlined via #24763 (comment), reproduced the issue where the Live Chat wasn't loading due to https://www.youtube.com/live_chat?continuation=... hanging/being in a Pending state as per the following:

reproducedIssue.mp4

Using the same STR/Cases as per the above, verified that the Live Chat was loading pretty quickly while using 1.70.51 Chromium: 127.0.6533.88 as per the following:

fixedIssueChat.mp4

• ensured that the video/audio loaded instantly without any issues/ads
• ensured that the Live Chat loaded instantly without any issues/crashes
• ensured that https://www.youtube.com/live_chat?continuation=... didn't get stuck in Pending state for ~15-30s.