fix: bump message signing snap to support portfolio automatic connections

[Prithpal-Sooriya]

Description

Bumps @metamask/message-signing-snap to 0.4.0 to allow portfolio to support automatic connections.

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/NOTIFY-1136

Manual testing steps

This does not effect anything within the wallet.

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.

[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/[email protected]	None	0	232 kB	metamaskbot
npm/[email protected]	None	0	667 kB	colinmcd94

🚮 Removed packages: npm/@metamask/[email protected], npm/[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 SonarCloud