Patch Chromium files to fix PIP behavior

[simoarpe]

Converting patches into bytecode. Draft PR - Not ready to review

Resolves brave/brave-browser#44287

Demo (with Sound)

2Screen.Recording.2025-02-28.at.6.28.09.PM.mov

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:

• Open Brave Browser and navigate to youtube.com
• Search for a random video and play it
• Rotate the device in landscape mode
• Navigate to the home screen using the swiping gestures
• Observe the activity playing the video entering into picture in picture mode
• Lock the screen
• Observe the audio keeps playing
• Unlock the screen
• Observe the activity is still correctly playing the video in picture in picture mode

[samartnik]

Why we need direct patches instead of bytecode ones? Are we planning to upstream it?

[simoarpe]

Happy to switch to bytecode approach. Moving this PR into a draft state.

[samartnik]

And one more quiestion, shouldn't it be apllied only for onHidden case? It feels like in other cases of calling exitPersistentFullscreenMode we shouldn't care of mTabHiddenByChangedTabs.

[simoarpe]

exitPersistentFullscreenMode method is called also by onActivityStateChange, so acting only on onHidden case would not prevent the activity from being reset into normal mode.