chore: bump @metamask/signature-controller to ^22.0.0

[cryptodev-2s]

Description

This PR bumps @metamask/signature-controller to ^22.0.0

Related issues

Fixes: #12307

Manual testing steps

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.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: cc9322a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/41302a76-af30-48d1-8b05-f3ea7a95e8df

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

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected]	network	+1	420 kB	metamaskbot

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

View full report↗︎

[sonarcloud]

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 SonarQube Cloud

[Gudahtt]

LGTM!

Similar to the preferences controller update PR, this introduces a new peer dependency warning but doesn't introduce any new risks.

The warning is due to this version requiring v18 of keyring-controller, but mobile uses v17. The only difference in v18 is the removal of addNewAccountWithoutUpdate, which the preferences controller does not use.

The warning will go away with #12339

[tommasini]

LGTM