Upgrade patches from Chromium 79.0.3945.88 to Chromium 79.0.3945.117 (uplift to 1.2)

[bsclifton]

Uplift of #4319
Fixes brave/brave-browser#7640
Related: brave/brave-browser#7646

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Android
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that these changes pass automated tests (unit, browser, security tests) on
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that all lint errors/warnings are resolved (npm run lint)
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone
• Public documentation has been updated as necessary. 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-Protection-Mode
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-compatibility-issues-with-tracking-protection
  • https://github.com/brave/brave-browser/wiki/QA-Guide

Test Plan:

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

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.

[kjozwiak]

@bsclifton looks like the only failure on Jenkins is on Linux due to https://ci.brave.com/job/brave-browser-build-pr/job/PR-7646/2/execution/node/547/log/ which is a known intermittent issue:

19:29:48  {"phase":2,"source":{"id":103,"type":8}]}
19:29:48                                         ^
19:29:48  
19:29:48  SyntaxError: Unexpected token ] in JSON at position 79101247
19:29:48      at JSON.parse (<anonymous>)
19:29:48      at start (/home/ubuntu/jenkins/workspace/brave-browser-build-pr_PR-7646/lib/start.js:144:23)
19:29:48      at Command.listener (/home/ubuntu/jenkins/workspace/brave-browser-build-pr_PR-7646/node_modules/commander/index.js:315:8)
19:29:48      at Command.emit (events.js:210:5)
19:29:48      at Command.parseArgs (/home/ubuntu/jenkins/workspace/brave-browser-build-pr_PR-7646/node_modules/commander/index.js:654:12)
19:29:48      at Command.parse (/home/ubuntu/jenkins/workspace/brave-browser-build-pr_PR-7646/node_modules/commander/index.js:474:21)
19:29:48      at Object.<anonymous> (/home/ubuntu/jenkins/workspace/brave-browser-build-pr_PR-7646/scripts/commands.js:158:4)
19:29:48      at Module._compile (internal/modules/cjs/loader.js:956:30)
19:29:48      at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
19:29:48      at Module.load (internal/modules/cjs/loader.js:812:32)

I'm not 100% sure about the Travis failure as per https://travis-ci.org/brave/brave-core/jobs/634008577?utm_medium=notification&utm_source=github_status.

[kjozwiak]

Uplift into 1.2.x approved after deliberating with @brave/uplift-approvers. CI/Jenkins failed on Linux as per #4320 (comment). However, it's a known intermittent issue that's been happening on Linux for sometime now and isn't associated with this particular PR.

Travis also failed as per https://travis-ci.org/brave/brave-core/jobs/634008577?utm_medium=notification&utm_source=github_status which isn't due to this particular PR.