feat: srp and key sync cp-7.52.0

[ieow]

Description

• Handle SRP and private key sync in social login flow
• check password outdated before import SRP/private key
• sync SRP/private key to metadata store when import
• sync multi SRP/private key to account when show SRP list

Changelog

CHANGELOG entry: Sync SRP from social account metadata store when open SRP list

Related issues

Fixes:
#17537
#17318

Manual testing steps

Rehydrate with all SRP/Private Key

1. Log in social account on a device (extension/mobile)
2. Add multiple SRP, Private Key to the account
3. On another mobile device, login to same account
4. All SRP, Private Key should be synced

Sync SRP/Private Key in logged in device

1. Login social account on a device (extension/mobile)
2. Login same account on another mobile device
3. Add new SRP/Private Key to the account
4. new SRP/Private Key should be synced to the first device
5. on the first device, add new SRP/Private Key
6. new SRP/Private Key should be synced to second mobile device

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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 3003fcf
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4b9ae024-c234-4696-8cfe-6591c80d57e5

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

[himanshuchawla009]

lgtm

[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.

[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.