chore(runway): cherry-pick fix: Ensure redux-persist-filesystem-storage returns a promise and throws correctly (#26979)

[runway-github]

• fix: Ensure redux-persist-filesystem-storage returns a promise and throws correctly cp-7.67.2 (fix: Ensure redux-persist-filesystem-storage returns a promise and throws correctly cp-7.67.2 cp-7.67.3 #26979)

Description

This PR adjusts our existing patch for
redux-persist-filesystem-storage to always return a promise for
setItem so it can be awaited correctly, fixing potential race
conditions. This was broken when the patch originally was created by
adding brackets to an arrow function and not returning. The PR also
fixes a bug where not passing in a callback would cause errors to be
swallowed. Additionally, this PR moves our existing patch to use the
built-in Yarn patch feature (because creating new patches with
patch-package seems broken).

Changelog

CHANGELOG entry: Improve reliability of persistence

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

Medium Risk
Touches persistence write behavior by changing the patched
redux-persist-filesystem-storage setItem control flow and error
propagation, which could affect app startup/migrations if any callers
depend on the old callback-only semantics. Also introduces an iOS-only
side effect (exclude-from-backup) after writes.

Overview
This PR updates the Yarn patch for redux-persist-filesystem-storage
so setItem always returns a Promise that can be awaited, rather
than potentially relying on callback chaining.

It also fixes error handling so write failures are thrown when no
callback is provided (instead of being swallowed), and adds an
optional isIOS flag to run
ReactNativeBlobUtil.ios.excludeFromBackupKey(...) after successful
writes on iOS.

Dependency wiring is switched from a normal semver dependency to
Yarn’s built-in patch: reference for
redux-persist-filesystem-storage@4.2.0, with corresponding yarn.lock
updates.

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

[02ac109](https://github.com/MetaMask/metamask-mobile/commit/02ac109fb36974ecfe3dbbdecc15b529bc2a8d17)

[github-actions]

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - base branch is not main (base: release/7.68.0)

All E2E tests pre-selected.

View GitHub Actions results