fix: re order migrations 105, 106, 107 cp-7.59.0

[tommasini]

Description

Re-order migrations 105, 106, 107

Removal of migration 104 redux-persist slicing. No longer needed

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

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.

---

Note

Reorders and repurposes migrations (104–106), removes 107, updates inflation/deflation thresholds, and aligns tests with the new behaviors.

• Migrations:
  • 104: Simplified to only reset PhishingController.urlScanCache; adds error reporting for invalid state.
  • 105: Now removes RatesController from engine.backgroundState; no-ops if absent; standardized error handling.
  • 106: Now cleans PPOM MMKV storage (PPOMDB); logic moved from former 107; returns unchanged state; error captured.
  • Removed: 107 migration and its tests.
  • Index (migrations/index.ts): Dropped 107 from migrationList; changed inflate trigger to > 106 and deflate on last version >= 106.
• Tests:
  • Updated/added tests for 104–106 reflecting new responsibilities and error messages.
  • Adjusted async migration flow tests to new version thresholds; removed old 107 tests; renamed for concision.

^{Written by Cursor Bugbot for commit a52e123. This will update automatically on new commits. Configure here.}

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

[MarioAslau]

LGTM

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud