feat: Add support for security alerts on zkSync, Berachain, Scroll and Metachain One on extension

[jpuri]

Description

Add support for security alerts on zkSync, Berachain, Scroll and Metachain One on extension

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/2716

Manual testing steps

1. Add networks zkSync, Berachain, Scroll and Metachain One to extension
2. Submit a malicious transaction on test dapp
3. Ensure it is reported as malicious

Screenshots/Recordings

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.

[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.

[jpuri]

Blockaid validations are not working as expected on these networks hence I add DO_NOT_MERGE to the PR.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@blockaid/[email protected]	network	0	3.34 MB	blockaiduser
npm/@metamask/[email protected]	Transitive: environment, filesystem, unsafe	+34	4.45 MB	metamaskbot

🚮 Removed packages: npm/@blockaid/[email protected], npm/@metamask/[email protected]

View full report↗︎

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[metamaskbot]

Builds ready [0bae4fb]

• 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 (72 ± 7 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	81	133	102	13	6
		domContentLoaded	10	60	30	11	5
		load	52	110	72	15	7
		domInteractive	10	60	30	11	5

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

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.57%. Comparing base (1f74b08) to head (0bae4fb).
Report is 28 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop   #25555   +/-   ##
========================================
  Coverage    69.57%   69.57%           
========================================
  Files         1360     1360           
  Lines        48172    48174    +2     
  Branches     13296    13296           
========================================
+ Hits         33513    33515    +2     
  Misses       14659    14659           

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