chore/ Update accounts-controller @v19.0.0 and keyring-controller @v18.0.0

[owencraston]

Description

This PR updates the accounts controller to the latest version of 19. This updates requires a peer dependancy bump of the keyring controller to version 18.0.0

• See accounts controller changelog.
• See keyring controller changelog.
  • version 18 of the keyring controller removes the addNewAccountWithoutUpdate which is used once in the mobile repo. In order to merge this PR we will need to wait for @mikesposito's PR to merge. This PR removes the need for addNewAccountWithoutUpdate and improves performance/reliability.

Related issues

Fixes: #12302
Fixes: #12304

Blocked by: #11409

Manual testing steps

Account creation

1. open app
2. press create wallet
3. go through the onboarding flow
4. once onboarding is complete, you should be on the wallet view and see a single account
5. open the account selector list and add a new account'
6. this should work without issues
7. change the name of your new account
8. force close the app and reopen, the previously selected account should be the same and the custom name should be preserved.

Account importing

1. assuming you have created a wallet wth the above steps....
2. open the account selector list and click add account or hardware wallet and then click import account
3. paste a private key in this text field and then import
4. the account should be imported, selected and have the label "imported"
5. force closing the app and re opening it should preserve the same state of accounts

Hardware wallets

1. assuming you have created a wallet wth the above steps....
2. open the account selector list and click add account or hardware wallet and then click Add hardware wallet
3. select your hardware wallet of choice (ledger or qr based)
4. follow the instructions to add a hardware wallet
5. the steps should work and you should have successfully added a hardware account
6. the hardware account should have the correct labels (either Qr hardware or ledger)
7. force closing the app and reopening should preserve the same accounts state.

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/[email protected]	None	0	267 kB	metamaskbot
npm/@metamask/[email protected]	None	0	221 kB	metamaskbot
npm/@metamask/[email protected]	Transitive: network	+3	3.17 MB
npm/@metamask/[email protected]	None	0	178 kB	metamaskbot
npm/@metamask/[email protected]	None	0	49.9 kB	metamaskbot
npm/@metamask/[email protected]	Transitive: environment	+2	630 kB	danfinlay, gudahtt, kumavis, ...7 more
npm/@metamask/[email protected]	Transitive: network	+3	2.86 MB	danfinlay, gudahtt, kumavis, ...7 more
npm/@metamask/[email protected]	None	0	1.23 MB	metamaskbot

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 24bfc6c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f8893ed8-ce7f-4e18-9e35-560f827dc7c3

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