Enabled ModuleFileNamePatch on Release channel.

[boocmp]

No description provided.

[github-actions]

✅ Test Seed Generated Successfully

To apply the test seed:

1. Desktop: Launch the browser with --variations-pr=1143.
   Android: Set the command line to --variations-pr=1143 in debug menu, restart the browser.
   iOS: Set Variations PR to 1143 in Brave Core Switches debug menu, restart the browser.
2. Wait 5-10 seconds to fetch the seed.
3. Restart the browser to apply the seed.
4. Ensure Active Variations section at brave://version starts with the expected seed version (see below).

Seed Details

• Version: pull/1143@431c83495ff38ea31c9824c4038d7f70b95e2d5c
• Uploaded: 2024-07-25T16:11:26.889Z
• Serial Number: abaaebb1697890e1915fb95497e8ec42

[kjozwiak]

LGTM 👍 Merging into main so QA can verify before pushing #1144 into production.

[kjozwiak]

Win x64 verification

Using the same STR/Cases outlined via #578 (comment).

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

Brave | 1.68.131 Chromium: 127.0.6533.73 (Official Build) (64-bit)
-- | --
Revision | 8167dd98e054f33ff258260aaf64d2eba8110772
OS | Windows 11 Version 23H2 (Build 22631.3958)

ModuleFileNamePatchStudy:Enabled

• launched 1.68.131 Chromium: 127.0.6533.73  using the terminal/CLI switch
  • brave.exe --enable-logging=stderr --variations-server-url=https://variations.bravesoftware.com/seed
• ensured that ModuleFileNamePatchStudy wasn't being displayed via brave://version
• restarted the browser and ensured that ModuleFileNamePatchStudy:Enabled via brave://version
• checked brave://gpu and ensured that all the paths under Executable path are pointing to chrome.exe

GetModuleFileNameExA = C:\Program Files\BraveSoftware\Brave-Browser\Application\chrome.exe
GetModuleFileNameExW = C:\Program Files\BraveSoftware\Brave-Browser\Application\chrome.exe
GetModuleFileNameA = C:\Program Files\BraveSoftware\Brave-Browser\Application\chrome.exe
GetModuleFileNameW = C:\Program Files\BraveSoftware\Brave-Browser\Application\chrome.exe

Example	Example

ModuleFileNamePatchStudy:Default

• launched 1.68.131 Chromium: 127.0.6533.73  using the terminal/CLI switch
  • brave.exe --enable-logging=stderr --variations-server-url=https://variations.bravesoftware.com/seed
• ensured that ModuleFileNamePatchStudy wasn't being displayed via brave://version
• restarted the browser and ensured that ModuleFileNamePatchStudy:Enabled via brave://version
• checked brave://gpu and ensured that all the paths under Executable path are pointing to brave.exe

GetModuleFileNameExA = C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe
GetModuleFileNameExW = C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe
GetModuleFileNameA = C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe
GetModuleFileNameW = C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe

Example	Example