chore: Improve Keyring/Accounts error handling and logs

[owencraston]

Description

This PR does the following

1. unmasks non sensitive data from the Accounts Controller and Keyring controller to help us better debug issues in prod. This means that more data will be provided in the sentry state logs. I have ensured that all addresses have remained masked
2. adds logs when creating key components such as the engine and the accounts controller. This will help us debug issues with empty state.
3. adds validation to the migrations for key components. Currently we are validating that the accounts controller and keyring controller data are sound. This validation will not block the app from initializing but will log the errors it finds.

Related issues

Progresses : #12408

Manual testing steps

1. this change only adds logs and error handling to the app so there should be no functional changes. that being said, we should still verify that the upgrade path is working.

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 failed on Bitrise! ❌❌❌

Commit hash: 4c958ed
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/af7f2b81-5142-4ee2-a670-5cd7bfd5055d

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

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 92.53731% with 5 lines in your changes missing coverage. Please review.

Project coverage is 59.11%. Comparing base (9d6908b) to head (7c6f385).
Report is 41 commits behind head on main.

Files with missing lines	Patch %	Lines
app/store/index.ts	0.00%	2 Missing ⚠️
app/core/Engine/Engine.ts	66.66%	1 Missing ⚠️
...re/Engine/controllers/AccountsController/logger.ts	75.00%	0 Missing and 1 partial ⚠️
app/core/Engine/utils/logger.ts	75.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12822      +/-   ##
==========================================
+ Coverage   58.85%   59.11%   +0.26%     
==========================================
  Files        1851     1859       +8     
  Lines       41739    41876     +137     
  Branches     5397     5436      +39     
==========================================
+ Hits        24566    24757     +191     
+ Misses      15502    15444      -58     
- Partials     1671     1675       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 327980c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8c2d0c55-c540-4a22-98f5-6627c740ba9c

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

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 5d25241
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ffe3c313-980c-4c77-b869-34064dd47391

Note

• This comment will auto-update when build completes
• 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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: a7ab7b4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/607cad82-eaba-4a4b-91ff-2d2ef277d364

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]

LGTM

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
3 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 760ffbd
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b91c7ad4-4278-4318-9157-17b1433f4927

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