chore: update bridge config to v2 (#5837)

## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

This PR consumes the new `bridgeConfigV2` field from LaunchDarkly.

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

Related to #5834, #5835

## Changelog

<!--
THIS SECTION IS NO LONGER NEEDED.

The process for updating changelogs has changed. Please consult the
"Updating changelogs" section of the Contributing doc for more.
-->

## Checklist

- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [x] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs),
highlighting breaking changes as necessary
- [x] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes

---------

Co-authored-by: Michele Esposito <[email protected]>
Co-authored-by: Bryan Fullam <[email protected]>

Author: 3 people

packages/bridge-controller/CHANGELOG.md

@@ -11,6 +11,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - **BREAKING:** Added a required `minimumVersion` to feature flag response schema ([#5834](https://github.com/MetaMask/core/pull/5834))
 
+### Changed
+
+- Consume `bridgeConfigV2` in the feature flag response schema for Mobile and export `DEFAULT_FEATURE_FLAG_CONFIG` ([#5837](https://github.com/MetaMask/core/pull/5837))
+
 ## [25.1.0]
 
 ### Added

packages/bridge-controller/src/index.ts

@@ -133,3 +133,5 @@ export {
   selectIsQuoteExpired,
   selectBridgeFeatureFlags,
 } from './selectors';
+
+export { DEFAULT_FEATURE_FLAG_CONFIG } from './constants/bridge';

packages/bridge-controller/src/utils/feature-flags.test.ts

@@ -356,5 +356,107 @@ describe('feature-flags', () => {
       };
       expect(result).toStrictEqual(expectedBridgeConfig);
     });
+
+    it('should prioritize bridgeConfigV2 over bridgeConfig', async () => {
+      const bridgeConfigV2 = {
+        refreshRate: 5,
+        maxRefreshCount: 2,
+        support: true,
+        minimumVersion: '1.0.0',
+        chains: {
+          '1': {
+            isActiveSrc: true,
+            isActiveDest: true,
+          },
+        },
+      };
+
+      const bridgeConfig = {
+        refreshRate: 3,
+        maxRefreshCount: 1,
+        support: true,
+        minimumVersion: '0.0.0',
+        chains: {
+          '1': {
+            isActiveSrc: true,
+            isActiveDest: true,
+          },
+        },
+      };
+
+      const remoteFeatureFlagControllerState = {
+        cacheTimestamp: 1745515389440,
+        remoteFeatureFlags: {
+          bridgeConfigV2,
+          bridgeConfig,
+          assetsNotificationsEnabled: false,
+        },
+      };
+
+      (mockMessenger.call as jest.Mock).mockImplementation(() => {
+        return remoteFeatureFlagControllerState;
+      });
+
+      const result = getBridgeFeatureFlags(mockMessenger);
+
+      const expectedBridgeConfig = {
+        refreshRate: 5,
+        maxRefreshCount: 2,
+        support: true,
+        minimumVersion: '1.0.0',
+        chains: {
+          'eip155:1': {
+            isActiveSrc: true,
+            isActiveDest: true,
+          },
+        },
+      };
+
+      expect(result).toStrictEqual(expectedBridgeConfig);
+    });
+
+    it('should fallback to bridgeConfig when bridgeConfigV2 is not available', async () => {
+      const bridgeConfig = {
+        refreshRate: 3,
+        maxRefreshCount: 1,
+        support: true,
+        minimumVersion: '0.0.0',
+        chains: {
+          '1': {
+            isActiveSrc: true,
+            isActiveDest: true,
+          },
+        },
+      };
+
+      const remoteFeatureFlagControllerState = {
+        cacheTimestamp: 1745515389440,
+        remoteFeatureFlags: {
+          bridgeConfig,
+          assetsNotificationsEnabled: false,
+        },
+      };
+
+      (mockMessenger.call as jest.Mock).mockImplementation(() => {
+        return remoteFeatureFlagControllerState;
+      });
+
+      const result = getBridgeFeatureFlags(mockMessenger);
+
+      const expectedBridgeConfig = {
+        refreshRate: 3,
+        maxRefreshCount: 1,
+        support: true,
+        minimumVersion: '0.0.0',
+        chains: {
+          'eip155:1': {
+            isActiveSrc: true,
+            isActiveDest: true,
+          },
+        },
+      };
+
+      expect(result).toStrictEqual(expectedBridgeConfig);
+    });
   });
 });

packages/bridge-controller/src/utils/feature-flags.ts

@@ -47,8 +47,18 @@ export function getBridgeFeatureFlags(
   const remoteFeatureFlagControllerState = messenger.call(
     'RemoteFeatureFlagController:getState',
   );
+
+  // bridgeConfigV2 is the feature flag for the mobile app
+  // bridgeConfig for Mobile has been deprecated since release of bridge and Solana in 7.46.0 was pushed back
+  // and there's no way to turn on bridgeConfig for 7.47.0 without affecting 7.46.0 as well.
+  // You will still get bridgeConfig returned from remoteFeatureFlagControllerState but you should use bridgeConfigV2 instead
+  // Mobile's bridgeConfig will be permanently serving the disabled variation, so falling back to it in Mobile will be ok
+  const rawMobileFlags =
+    remoteFeatureFlagControllerState?.remoteFeatureFlags?.bridgeConfigV2;
+
+  // Extension LaunchDarkly will not have the bridgeConfigV2 field, so we'll continue to use bridgeConfig
   const rawBridgeConfig =
     remoteFeatureFlagControllerState?.remoteFeatureFlags?.bridgeConfig;
 
-  return processFeatureFlags(rawBridgeConfig);
+  return processFeatureFlags(rawMobileFlags || rawBridgeConfig);
 }