Update wrong GOOGLE_CHROME_BUILD usage (uplift to 0.72.x)

[brave-builds]

Uplift of #3718
Fixes brave/brave-browser#6497
Fixes brave/brave-browser#6496

Approved, please ensure that before merging:

• You have checked CI and the builds, lint, and tests all pass or are not related to your PR.
• You have tested your change on Nightly.
• The PR milestones match the branch they are landing to.

After you merge:

• The associated issue milestone is set to the smallest version that the changes is landed on.

[kjozwiak]

@bsclifton looks like lint failed on android, iOS, linux. macOS:

• android --> https://staging.ci.brave.com/job/brave-browser-build-pr/job/pr3718_fix_vmp_not_working_0.72.x/1/execution/node/277/log/
• iOS --> https://staging.ci.brave.com/job/brave-browser-build-pr/job/pr3718_fix_vmp_not_working_0.72.x/1/execution/node/572/log/
• linux --> https://staging.ci.brave.com/job/brave-browser-build-pr/job/pr3718_fix_vmp_not_working_0.72.x/1/execution/node/235/log/
• macOS --> https://staging.ci.brave.com/job/brave-browser-build-pr/job/pr3718_fix_vmp_not_working_0.72.x/1/execution/node/650/log/

Should we restart these PR's on android, iOS, linux. macOS or is this a known intermittent issue?

[bsclifton]

@kjozwiak we're OK skipping. It's a known issue captured here: brave/brave-browser#6434

It doesn't always seem to happen, which is weird

[kjozwiak]

Uplift into 0.72.x approved after deliberating with @brave/uplift-approvers. Please make sure that all the correct labels are being used and the associated issue is moved into the correct milestone.