fix: reset streams on prerender only for affected browser versions

[jiexi]

Description

The prerender regression in chromium has been resolved already. Resetting streams on prerendered pages no longer required for newer chromium versions and is actually the cause of unresponsive provider in many cases. This PR modifies the existing workaround to target only the affected chromium ranges from >=113 to <121.

My bisection of chromium for the fix landed on this range of commits: https://chromium.googlesource.com/chromium/src/+log/55b4344edfb41dda980d197743f25a2841d498a4..c13107c16780c195bd5ec003d9198d87cdcc59dd

@shanejonas and I have verified that the prerender issue has been resolved in the latest chrome stable. I have verified that the workaround is causing an issue in develop that is no longer seen in this branch that reverts it.

Related issues

See: #19727

Manual testing steps

Using chrome, of course.
Visit chrome://settings/?search=preload and ensure it is enabled and on "standard"

1. On develop, make a build and load it
2. Visit https://voyager-snap.linea.build/
3. Install the snap and connect
4. Copy https://voyager-snap.linea.build/ to your clipboard
5. Close all instances of https://voyager-snap.linea.build/ that may be open
6. Rapidly, open a new tab, paste the url, hit enter, see if the page is stuck on "Loading", if not close the tab and repeat
7. Eventually the page should be get prerendered and stuck in a broken state

Do the same steps above, but using the changes in this branch. The page should never be stuck with "Loading" if you are on a chromium version from 102 to 112, or 121 onwards.

Screenshots/Recordings

Before

Screen.Recording.2024-04-29.at.11.34.02.AM.mov

After

Screen.Recording.2024-04-29.at.11.32.27.AM.mov

Browser version targeting proof

The following screenshots show the return value for getIsBrowserPrerenderBroken() on various chromium versions

120:

119:

113:

112:

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[metamaskbot]

Builds ready [7f7b46b]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8
  • content-script: 0
  • ui: 0, 1, 10, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (547 ± 472 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	56	104	74	14	7
		domContentLoaded	8	28	11	4	2
		load	46	2722	547	983	472
		domInteractive	8	28	11	4	2

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 0 Bytes (0.00%)
• ui: 0 Bytes (0.00%)
• common: 687 Bytes (0.01%)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.32%. Comparing base (2c45770) to head (08279ef).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #24317      +/-   ##
===========================================
+ Coverage    67.31%   67.32%   +0.01%     
===========================================
  Files         1276     1276              
  Lines        49731    49739       +8     
  Branches     12921    12925       +4     
===========================================
+ Hits         33474    33482       +8     
  Misses       16257    16257              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Gudahtt]

Probably we could treat Opera 99-(107?) as affected as well, but maybe not worth worrying about given the impact of the bug. We can adjust this later if we need to. Who knows what they're changing in their fork.

[Gudahtt]

LGTM!

[adonesky1]

LGTM! Thanks for so much great digging here @jiexi!

[metamaskbot]

Builds ready [08279ef]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8
  • content-script: 0
  • ui: 0, 1, 10, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (508 ± 537 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	56	149	79	28	13
		domContentLoaded	8	49	12	9	4
		load	45	4142	508	1118	537
		domInteractive	8	49	12	9	4

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 0 Bytes (0.00%)
• ui: 0 Bytes (0.00%)
• common: 687 Bytes (0.01%)