feat: sdk async key exchange

[abretonc7s]

Description

• Full async key exchange implementation for SDK with update of comm layer.
  
• Full documentation at https://www.notion.so/metamask-consensys/e3cb7482a492445fb0665334e53a1795?v=34d0d322d99f493aaf7b1ac58ed1c87b&p=2c95933da20e465fa0eeeed48adb9e68&pm=s

Related issues

Fixes: #10315

Manual testing steps

1. Go to this page...

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]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/sdk-communication-layer@0.28.1	None	0	3.16 MB	danfinlay, gudahtt, kumavis, ...8 more
npm/utf-8-validate@5.0.10	None	0	403 kB	lpinca

🚮 Removed packages: npm/@metamask/sdk-communication-layer@0.20.2), npm/utf-8-validate@6.0.3)

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/utf-8-validate@5.0.10

View full report↗︎

Next steps

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

[abretonc7s]

@SocketSecurity ignore npm/utf-8-validate@5.0.10
In the process of fully removing the depency from the communication layer

[christopherferreira9]

Full testing strategy and results here.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 586c4b1
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4b35f15c-d2f5-4b50-8c89-fac53734c9db

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

[christopherferreira9]

E2E are currently experiencing flaky results:
The first run had 4 tests failing: https://app.bitrise.io/build/b1fb0923-0428-4e22-815d-d4b9b7ef6989
The second run had only 2 tests failing: https://app.bitrise.io/build/0bab6409-fa2a-42b1-9922-ed93b7809406

No fixes were done in between the two runs

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: d2f6ce0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f6365f89-7c23-42aa-871e-760323463667

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

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[christopherferreira9]

E2E passing here: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c0c9ddbb-a272-4622-9b17-33da70728e3e