fix: @metamask/swaps-controller v6 -> v9

[legobeat]

Description

• Upgrade @metamask/swaps-controller from v8 to v9
  • Remove redundant patches

Resolves a bunch of outstanding legacy, including web-provider-engine.

Also enables Base Network for Swaps.

Related issues

• feat(swaps): enable Base for swaps #9286 @metamask/swaps-controller
  • v8 upgrade
• revert: feat(swaps): enable Base for swaps (#9286) #9612
  • reverted v8 upgrade
• https://github.com/MetaMask/swaps-controller/pull/241
  • fixed issue that motivated revert of v8 upgrade

Blocked by

• https://github.com/MetaMask/swaps-controller/pull/245
  • https://github.com/MetaMask/swaps-controller/pull/219

Manual testing steps

Screenshots/Recordings

Before

After

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.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/swaps-controller@9.0.0	Transitive: filesystem, network	+45	43.6 MB
npm/crc-32@1.2.2	None	0	31 kB	sheetjs
npm/web3-core@4.4.0	Transitive: filesystem, network	+9	2.87 MB	luu-alex
npm/web3-errors@1.2.0	None	0	416 kB	luu-alex
npm/web3-eth@4.7.0	None	+10	36.8 MB	luu-alex
npm/web3-rpc-methods@1.3.0	None	0	135 kB	luu-alex
npm/web3-types@1.6.0	None	0	300 kB	luu-alex
npm/web3-utils@4.3.0	None	+1	607 kB	luu-alex
npm/web3-validator@2.0.6	None	0	957 kB	luu-alex
npm/xhr2@0.2.1	network	0	137 kB	pwnall
npm/zod@3.23.8	None	0	667 kB	colinmcd94

🚮 Removed packages: npm/@metamask/swaps-controller@6.9.3, npm/bip39@2.6.0, npm/eth-sig-util@3.0.1, npm/web3-provider-engine@16.0.8

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Network access	npm/web3-providers-http@4.1.0	Module: globalThis["fetch"] Location: Package overview	package.json
Network access	npm/web3-providers-ipc@4.0.7	Module: net Location: Package overview	Source
Network access	npm/web3-providers-ipc@4.0.7	Module: net Location: Package overview	Source
New author	npm/web3-eth-personal@4.0.8	New Author: luu-alex Previous Author: mpetrunic	package.json
Unstable ownership	npm/web3-errors@1.2.0	Author: luu-alex	Source
New author	npm/web3-errors@1.2.0	New Author: luu-alex Previous Author: mpetrunic	Source
Unstable ownership	npm/web3-net@4.1.0	Author: luu-alex	package.json
New author	npm/web3-net@4.1.0	New Author: luu-alex Previous Author: mpetrunic	package.json

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What is unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

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

• @SocketSecurity ignore npm/web3-providers-http@4.1.0
• @SocketSecurity ignore npm/web3-providers-ipc@4.0.7
• @SocketSecurity ignore npm/web3-eth-personal@4.0.8
• @SocketSecurity ignore npm/web3-errors@1.2.0
• @SocketSecurity ignore npm/web3-net@4.1.0

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 2adf95f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ebcc7bec-2a7b-4f03-87fb-50de0a90d192

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: e7841ee
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/39fa6918-d553-4017-8502-c0f87ace6696

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 858ffe9
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/625931f0-676c-4108-af9c-048cedd183f4

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request