Bump MetaMask SDK version to 0.26.5

[christopherferreira9]

This PR bumps the MetaMask SDK version to 0.26.5 which features the new async protocol.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/json-rpc-engine@8.0.2	None	0	189 kB	metamaskbot
npm/@metamask/json-rpc-middleware-stream@7.0.2	None	0	78.4 kB	metamaskbot
npm/@metamask/providers@16.1.0	None	0	358 kB	metamaskbot
npm/@metamask/sdk-communication-layer@0.26.4	environment	0	3.04 MB	metamaskbot
npm/@metamask/sdk-install-modal-web@0.26.5	None	0	550 kB	metamaskbot
npm/@metamask/sdk@0.26.5	None	0	29.4 MB	metamaskbot
npm/i18next@23.11.5	None	0	635 kB	adrai
npm/utf-8-validate@5.0.10	None	0	403 kB	lpinca

🚮 Removed packages: npm/@metamask/json-rpc-engine@7.3.3, npm/@metamask/json-rpc-middleware-stream@6.0.2, npm/@metamask/providers@15.0.0, npm/@metamask/sdk-communication-layer@0.18.5, npm/@metamask/sdk-install-modal-web@0.18.5, npm/@metamask/sdk@0.18.6, npm/i18next@22.5.1, npm/utf-8-validate@6.0.3

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	CI
Native code	npm/utf-8-validate@5.0.10	Location: Package overview	yarn.lock	🚫

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

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/utf-8-validate@5.0.10

[elefantel]

Looks good