fix: handle potential undefined primary keyring when the app is locked cp-7.52.0

[montelaidev]

Description

This PR fixes the issue where accounts is undefined when the app auto locks while on the wallet details screen.

Changelog

CHANGELOG entry: null

Related issues

Fixes: #17522

Resolves: https://consensyssoftware.atlassian.net/browse/MUL-454?atlOrigin=eyJpIjoiYzMyNDZhYTQxMTBjNGNiYWE3ZWMzMjE5M2JkZjI1MDEiLCJwIjoiaiJ9

Manual testing steps

1 .import a wallet
2. click on the selected account
3. the account list should open
4. click the three dots beside any of your accounts
5. the account details page should open
6. click on the wallet section of the account details page
7. the wallet details page should open
8. do not touch the screen and let your phone screen auto lock
9. wait a few more seconds while the phone is unlocked
10. re open your phone
11. You will see the login screen

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.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 07d5a20
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/66a188f5-4594-4189-926c-707ec64bd1c7

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
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[owencraston]

Confirmed this fixes the crash in my testing.

[metamaskbot]

Missing release label release-7.52.0 on PR. Adding release label release-7.52.0 on PR and removing other release labels(release-7.53.0), as PR was cherry-picked in branch 7.52.0.