feat: bump controllers related accounts logic

[gantunesr]

Description

The original PR is #9318. It was reverted and now the changes are being introduced in this new PR.

This PR updates several controllers that handle logic related to the wallet and accounts.

• Keyring controller to v13
• Accounts Controller to v11
• Preferences controller v8

Some noteworthy points for this changes,

• Downgrade controller utils to interact with linea sepolia, only function used by preferences controller of controller-utils is toChecksumHexAddress and the function is the same on v^5 and on v^8
• Updated flow of create account and import account to update the ecnryptionLib that way on the future we can create or import and we will not run the flow [recreateVaultWithSamePassword](https://github.com/MetaMask/metamask-mobile/blob/fcfa9d1bd03e16ba18f3e9919b85a854614c2377/app/core/Authentication/Authentication.ts#L110), since it was running unnecessarily
• Updated controllers initialization that had preferencesOnStateChange argument on their constructor (Mostly assets-controllers and PPOM), to have the address checksummed, on this current version PreferencesController starts to listen to KeyringController and that address is now on lower case format, which means that we need to update to a checksummed format for those specific scenarios for the assets controllers keep their data and tokens never disappear from the user for missmatching user address format
• Updated keyring controller patch with the same as extension to prevent the HD wallet disappear, please check the details on this core branch: extension-keyring-controller-v13-patch

Related issues

• Fixes https://github.com/MetaMask/mobile-planning/issues/1689
• Fixes https://github.com/MetaMask/mobile-planning/issues/1697
• Fixes https://github.com/MetaMask/mobile-planning/issues/1693

Manual testing steps

1. Create new wallet
2. Import existing wallet
3. Import private key
4. Upgrade testing

Screenshots/Recordings

Upgrade from main with Binance Smart Chain Selected, imported account with private key and tokens imported (Multiple chains added, and tokens imported on them also NFT imported on mainnet)

Screen.Recording.2024-04-24.at.13.01.08.mov

Pre-merge author checklist

• I’ve followed MetaMask 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.

[gantunesr]

Bug reported in original PR,

Ran migration tests with a QA build of v7.18.0 (1268) to a QA build of commit 869cd17 and noted some accounts that were lost: Have before and after state logs available on 3 unique devices. All three devices lost the Ledger account, and 2 of 3 devices(both android and iOS) lost multiple QR accounts.

Follow up notes:
Before and After Statelogs here

This seems to be sporadic, as I have not been able to reproduce it with the same devices and the same 7.18.0 QA build like the initial observation.

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarCloud

[plasmacorral]

CONFIRMED NOT RELATED TO CHANGES IN THIS PR:

When importing a valid private key by QR code, user is shown an error: "Invalid deeplink Invalid URL:" and the private key string is displayed in the error message. The account is successfully imported, but the error message is not appropriate in this scenario.

Was observed with QA build from PR 9318, with multiple devices:

• Pixel 5a- Android 14
• Samsung a515f- Android 12
• iPhone Xs- iOS 17.4.1

Steps:

1. Import an SRP and get to wallet view
2. Follow add account flow for importing private key
3. Scan QR of valid private key
4. Observe error

UPDATE: This is present on main commit 6cc76b2 and is not related to the changes in this PR. This is not present on 7.21.0 build (production) but is present on the RC for 7.22.0. Opened a fresh issue.

[plasmacorral]

Tested migrations on Android 12, 14 and iOS 17.4.1 with Imported, Ledger and QR accounts present from both 7.18.0 (1268) as well as 7.19.0 (1292). Custom labels were preserved. Able to add and remove accounts as expected, change password and biometric auth, create new wallet, import an existing SRP in setup, import private keys after setup, and confirm SRP backup demand when value is added.

Had some observations, but was not able to reproduce outside of the initial occurrence and looks like there have been subsequent changes in both 7.19.0 and 7.20.0 that may resolve the issues observed.

• Observed accounts disappear once updating from 7.18.0 to the branch under test
  • There were two independent fixes for both Ledger and QR wallets both going missing, within 7.19.0
• Observed tokens disappear once on an imported account updating from 7.19.0 to the branch under test
  • There was a fix for disappearing tokens within 7.20.0
• Observed private key input appearing in an error message when importing by QR
  • was present on main and looks like it may have been introduced within 7.22.0, so filed a fresh report here

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 23506e2
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/009ba7f0-021f-44d4-9e05-64121d2fed65

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

[Cal-L]

E2E failure not related to this branch since it's failing because of notification prompt

[Cal-L]

LGTM