chore: bump network-controller preview to force failover build

[cryptodev-2s]

Description

Bumps the @metamask/network-controller preview build to 32.0.0-preview-eca6f2051, which adds the forced RPC failover capability.

When the core-platform-rpc-failover-force-enabled remote feature flag is on, any Infura endpoint that has failover URLs routes all of its traffic (including block tracker polling) to those failover URLs and never contacts Infura. It is an emergency kill switch for cases where the automatic failover logic itself misbehaves, and it works independently of the existing walletFrameworkRpcFailoverEnabled flag.

No app code changes are needed: network-controller reads the flag itself through RemoteFeatureFlagController, the networks already carry failover URLs, and the change is non breaking. This PR is just the dependency bump so the capability is available once the LaunchDarkly flag is created and enabled.

Core PR: MetaMask/core#9175

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/WPC-1112

Manual testing steps

Feature: Forced RPC failover

  Scenario: forced failover routes Infura traffic to the failover endpoint
    Given the core-platform-rpc-failover-force-enabled remote flag is on
    And the selected network is an Infura network with failover URLs configured
    When the app makes RPC requests on that network
    Then the requests go to the failover endpoint and not to Infura

  Scenario: turning the flag off restores Infura
    Given the core-platform-rpc-failover-force-enabled remote flag is off
    When the app makes RPC requests on an Infura network
    Then the requests go to Infura as usual

Screenshots/Recordings

N/A, dependency bump with no UI changes.

Before

N/A

After

N/A

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​metamask/​network-controller@​32.0.0-preview-22ab7e3 ⏵ 32.0.0-preview-eca6f2051

View full report