chore: bump @metamask/keyring-{snap-client,internal-api} versions

[ccharly]

Explanation

Some of the versions were not "aligned", resulting in different keyring-api versions (nothing too breaking though), but this sometimes pollutes the lavamoat policy files once updating the controllers on the extension, so it's "better" to keep them aligned as much as we can.

Was:

├─ @metamask/assets-controllers@workspace:packages/assets-controllers
│  ├─ @metamask/keyring-api@npm:17.0.0 (via npm:^17.0.0)
│  ├─ @metamask/keyring-internal-api@npm:4.0.2 (via npm:^4.0.1)
│  └─ @metamask/keyring-snap-client@npm:3.0.3 [d7116] (via npm:^3.0.3 [d7116])
│     └─ @metamask/keyring-api@npm:16.1.0 (via npm:^16.1.0)
...
├─ @metamask/multichain-transactions-controller@workspace:packages/multichain-transactions-controller
│  ├─ @metamask/keyring-api@npm:17.0.0 (via npm:^17.0.0)
│  ├─ @metamask/keyring-controller@workspace:packages/keyring-controller (via npm:^19.1.0)
│  ├─ @metamask/keyring-internal-api@npm:4.0.2 (via npm:^4.0.1)
│  └─ @metamask/keyring-snap-client@npm:3.0.3 [f7262] (via npm:^3.0.3 [f7262])
│     └─ @metamask/keyring-api@npm:16.1.0 (via npm:^16.1.0)

While the keyring-api being used everywhere else is the 17.0.0.

References

• chore: add @metamask/multichain-network-controller metamask-extension#30309

Changelog

See PR's content.

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[socket-security]

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: npm/@metamask/keyring-snap-client@3.0.3

View full report↗︎

[cryptodev-2s]

LGTM!