feat: update accounts-deps to enable KeyringRequest.origin support

[ccharly]

Description

Aligning some accounts deps to enable the new KeyringRequest.origin support for Keyring.submitRequest (from @metamask/keyring-api@18.0.0) and the multichain API.

Related issues

N/A

Manual testing steps

Using native swap/bridge (which rely on keyring_submitRequest):

1. Enable MM_BRIDGE_ENABLED="true" on you env files
2. Re-build and load the app
3. Use an SRP that have some Solana "funds"
4. Run the bridge flow using a Solana account
5. Run the swap flow using a Solana account

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile 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]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​metamask/​keyring-internal-snap-client@​4.0.2 ⏵ 4.1.0			+1	-1
	npm/​@​metamask/​keyring-internal-api@​6.0.1 ⏵ 6.2.0	+1		+2	-1
	npm/​@​metamask/​keyring-snap-client@​5.0.0
	npm/​@​metamask/​snaps-rpc-methods@​12.3.0 ⏵ 12.4.0
	npm/​@​metamask/​snaps-utils@​9.3.0 ⏵ 9.4.0			+1
	npm/​@​metamask/​snaps-controllers@​12.2.0 ⏵ 12.3.1	-7		-26	-1	-50
	npm/​@​metamask/​accounts-controller@​29.0.1 ⏵ 30.0.0	-2			+1
	npm/​@​metamask/​snaps-execution-environments@​8.1.0 ⏵ 8.2.0	+3
	npm/​@​metamask/​keyring-controller@​22.0.0 ⏵ 22.0.1	+3
	npm/​@​metamask/​signature-controller@​28.0.0 ⏵ 30.0.0	+2			+1
	npm/​@​metamask/​snaps-sdk@​7.1.0
	npm/​@​metamask/​transaction-controller@​56.3.0 ⏵ 57.1.0	+4		+1	+1
	npm/​@​metamask/​profile-sync-controller@​14.0.0 ⏵ 16.0.0
	npm/​@​metamask/​notification-services-controller@​7.0.0 ⏵ 9.0.0	+2
	npm/​@​metamask/​keyring-api@​18.0.0
	npm/​@​metamask/​eth-snap-keyring@​12.1.1 ⏵ 13.0.0			+1	+1
	npm/​@​metamask/​slip44@​4.1.0 ⏵ 4.2.0	+3		+1

View full report

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: b1176c9
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8b6aa588-ffac-4b24-9d07-22cd845d797b

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: ba0b20e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/3ecd219f-604d-4ddf-a728-dcf4de52dbe5

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 passed on Bitrise! ✅✅✅

Commit hash: 160c40f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ed40de59-7336-400d-8566-0f306772cbe6

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

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 70.72%. Comparing base (ab54792) to head (160c40f).
Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
app/core/Snaps/SnapsMethodMiddleware.ts	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15995      +/-   ##
==========================================
- Coverage   70.73%   70.72%   -0.01%     
==========================================
  Files        2570     2570              
  Lines       54858    54867       +9     
  Branches     8451     8454       +3     
==========================================
+ Hits        38802    38806       +4     
- Misses      13587    13589       +2     
- Partials     2469     2472       +3     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[gantunesr]

app/core/SnapKeyring/types.ts ✅

[ccharly]

I ran some manual tests around the concerned areas and I could not notice any regression (hence de No-QA label)

[tommasini]

Should we align as well the metamask/providers repo version? https://github.com/MetaMask/core/blob/d913b909a1473b1f446224dfdefc5141f0943ad3/packages/accounts-controller/package.json#L82

[ccharly]

Should we align as well the metamask/providers repo version?

Good question! And I believe we should do it at some point!

I'm just not sure what this implies though... I believe that's fine to keep it as-is for now, given that the previous version of the accounts-controller was already depending on another @metamask/providers version that was not aligned with the one currently in use here 😅:

• https://github.com/MetaMask/core/blob/%40metamask/accounts-controller%4029.0.1/packages/accounts-controller/package.json#L82

I also don't know who owns this kind of upgrade TBH.