Backporting --ozone-platform-hint fix

[cdesouza-chromium]

This change is landing in down the line in chromium upstream, but for the moment current users of 1.66.x and 1.65.x are being affected.

https://chromium-review.googlesource.com/c/chromium/src/+/5375669

Chromium change:
https://chromium.googlesource.com/chromium/src/+/c7f4c58f896a651eba80ad805ebdb49d19ebdbd4

commit c7f4c58f896a651eba80ad805ebdb49d19ebdbd4
Author: Tom Anderson [email protected]
Date: Wed Mar 20 00:00:12 2024 +0000

Fix --ozone-platform-hint

This fixes a regression after r1269993 which moved ozone platform
early initialization before the ozone platform hint flag was
processed.  This CL ensures the flag processing happens even earlier.

R=sky

Change-Id: Icc9649beb0b86753265be2b6cdf3059611eb410f
Bug: None

Resolves brave/brave-browser#37498

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:

[github-actions]

The following commits were not verified:
575b3b0 (unsigned)

[kjozwiak]

Verification PASSED on Fedora 39 x64 using the following build(s):

Brave | 1.67.26 Chromium: 124.0.6367.60 (Official Build) nightly (64-bit)
--- | ---
Revision | fb129438acc3c97a8676d7e77cf0b40925e46aad
OS | Linux

Reproduced the original issue by setting ozone-platform-hint to Wayland via brave://flags as per the following:

Example	Example

Once reproduced, downloaded/installed 1.67.26 Chromium: 124.0.6367.60 and ensured that Brave was being opened and rendering websites without any issues while ozone-platform-hint was set as Wayland. Also ensured that the default installation worked without any issues.