Description

This change removes the log where it's falsely reporting failed vault back up when the keyring controller state changes for two reasons:

• A state change of the keyring controller by itself is not sufficient to indicate a vault corruption
• The keyring controller experiences state changes where the vault property is removed in the middle of a new wallet creation

The failure reports happen twice when a new wallet is created

We can remove the log here since there is already a failure condition during log in where it reports a missing vault

Related issues

Fixes: Bugs (deprecated)

Manual testing steps

1. Install this branch
2. Create new wallet
3. No false reporting of a failed vault back up should occur
4. Unit test for backupVault simulates what the failed case will report

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.