chore: upgrade to Sentry 8 (#25999) [cherry-pick]

[Gudahtt]

This PR cherry-picks #25999 to v12.1.0. Original description:

Description

Upgrade the Sentry packages from 7.53.0 to 8.19.0.

Specifically:

• Refactor custom FilterEvents integration into object returned by function.
• Remove usages of hub.
• Fix notification errors when changing metrics preference.

Related issues

Manual testing steps

Full Sentry regression.

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension 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.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@sentry-internal/browser-utils@8.19.0	network	0	663 kB	sentry-bot
npm/@sentry-internal/feedback@8.19.0	None	0	555 kB	sentry-bot
npm/@sentry-internal/replay-canvas@8.19.0	None	0	531 kB	sentry-bot
npm/@sentry-internal/replay@8.19.0	None	0	3.73 MB	sentry-bot
npm/@sentry/browser@8.19.0	network	0	956 kB	sentry-bot
npm/@sentry/core@8.19.0	network	0	1.89 MB	sentry-bot
npm/@sentry/types@8.19.0	None	0	329 kB	sentry-bot
npm/@sentry/utils@8.19.0	network	0	1.14 MB	sentry-bot

🚮 Removed packages: npm/@sentry-internal/tracing@7.53.0), npm/@sentry/browser@7.53.0), npm/@sentry/core@7.53.0), npm/@sentry/integrations@7.53.0), npm/@sentry/replay@7.53.0), npm/@sentry/types@7.53.0), npm/@sentry/utils@7.53.0)

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@sentry-internal/browser-utils@8.19.0, npm/@sentry/core@8.19.0, npm/@sentry/utils@8.19.0

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[Gudahtt]

@metamaskbot update-policies

[Gudahtt]

For reviewers, I would recommend reviewing the code to make sure I didn't make any mistakes when merging conflicts, but we can save manual testing for later. There are three Sentry-related PRs we will be cherry-picking in, which this is the first of. We can do a full Sentry regression test on all three changes together.

[metamaskbot]

Policies updated

[Gudahtt]

@SocketSecurity ignore npm/@sentry-internal/browser-utils@8.19.0
@SocketSecurity ignore npm/@sentry/core@8.19.0
@SocketSecurity ignore npm/@sentry/utils@8.19.0

These are intended to have network access

[metamaskbot]

Builds ready [5d4bd9d]

• 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
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (148 ± 142 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	66	276	117	56	27
		domContentLoaded	9	173	34	37	18
		load	39	1414	148	295	142
		domInteractive	9	173	34	37	18

[codecov]

Codecov Report

Attention: Patch coverage is 18.18182% with 18 lines in your changes missing coverage. Please review.

Project coverage is 69.83%. Comparing base (4d299d8) to head (5d4bd9d).
Report is 1 commits behind head on Version-v12.1.0.

Files	Patch %	Lines
app/scripts/lib/setupSentry.js	0.00%	11 Missing ⚠️
app/scripts/lib/sentry-filter-events.ts	12.50%	7 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           Version-v12.1.0   #26618   +/-   ##
================================================
  Coverage            69.83%   69.83%           
================================================
  Files                 1368     1368           
  Lines                48655    48653    -2     
  Branches             13435    13434    -1     
================================================
+ Hits                 33974    33975    +1     
+ Misses               14681    14678    -3     

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

[metamaskbot]

No release label on PR. Adding release label release-12.2.0 on PR, as PR was cherry-picked in branch 12.2.0.