fix: Create migration 59 to fix undefined selectedAccount

[Cal-L]

Description

This PR addresses a crasher related to an undefined selectedAccount causing the AccountsController to throw an error. Under this scenario, the solution is to set selectedAccount to an empty string, which the AccountsController will automatically reset the selectedAccount.

PR similar to #11866 but not the same

Related issues

Fixes: #11488

Manual testing steps

1. Building on main, create a wallet and kill the app
2. Create a migration that sets selectedAccount on the AccountsController to be undefined
3. Run the app, notice it encounters the error. Kill the app
4. Run this branch, which includes migration 59. Notice you are no longer blocked and can log in
5. Will see an account selected by default after landing on wallet

Screenshots/Recordings

Before

The error that users eventually see as a result of the migration failures

After

After applying migration
https://github.com/user-attachments/assets/e959c8d9-5dfd-4b69-8f4d-16689bf66d95

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.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 1955898
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/6b487a9b-349a-4f8c-9e52-d5e625a829e1

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[Cal-L]

Bitrise failure not related to this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud