chore(runway): cherry-pick refactor: simplify rampsUnifiedBuyV2 feature flag to single selector cp-7.71.0

[runway-github]

• refactor: simplify rampsUnifiedBuyV2 feature flag to single selector cp-7.71.0 (refactor: simplify rampsUnifiedBuyV2 feature flag to single selector cp-7.71.0 #27760)

Description

The rampsUnifiedBuyV2 feature flag previously used three chained
selectors (selectRampsUnifiedBuyV2Config →
selectRampsUnifiedBuyV2ActiveFlag /
selectRampsUnifiedBuyV2MinimumVersionFlag) and a custom 2-arg
hasMinimumRequiredVersion utility. This was inconsistent with how
other feature flags (e.g. homepage redesign) are handled in the
codebase.

This PR consolidates the three selectors into a single
selectRampsUnifiedBuyV2Enabled selector that uses the shared
validatedVersionGatedFeatureFlag utility from
app/util/remoteFeatureFlag. The remote flag shape is updated from { active, minimumVersion } to { enabled, minimumVersion } to match the
standard VersionGatedFeatureFlag type.

Key changes:

• Selector file (rampsUnifiedBuyV2.ts): Replaced 3 selectors +
  RampsUnifiedBuyV2Config interface with a single
  selectRampsUnifiedBuyV2Enabled selector
• Hook (useRampsUnifiedV2Enabled.ts): Simplified from two
  useSelector calls + hasMinimumRequiredVersion to a single
  useSelector
• Utility (isRampsUnifiedV2Enabled.ts): Simplified to delegate
  directly to the selector
• Controller init (ramps-controller-init.ts): Replaced local
  interface + hasMinimumRequiredVersion with
  validatedVersionGatedFeatureFlag; imports shared flag key constant
• Flag key constant: Exported RAMPS_UNIFIED_BUY_V2_FLAG_KEY from
  the selector file as single source of truth
• E2E mocks/fixtures: Updated flag shape from active to enabled
  in FixtureBuilder, feature-flags-mocks, and feature-flag-registry

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

N/A — this is a pure refactor of internal selector structure. Behavior
is unchanged. All unit tests have been updated and pass.

Screenshots/Recordings

Before

N/A

After

ff.mp4

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 feature-flag gating that controls whether the ramps V2 flow
and controller initialization run, and changes the expected remote flag
shape from active to enabled. Main risk is misconfigured/older flag
payloads causing the feature to be incorrectly disabled.

Overview
Simplifies rampsUnifiedBuyV2 enablement checks by replacing the
chained config/active/min-version selectors and custom gating logic with
a single selectRampsUnifiedBuyV2Enabled that delegates to
validatedVersionGatedFeatureFlag.

Updates the Ramp hook/utility and ramps-controller-init to consume
this unified version-gated flag (keeping the build-flag override), and
standardizes the remote flag payload from { active, minimumVersion }
to { enabled, minimumVersion } across unit tests, E2E mocks/fixtures,
and the feature-flag registry defaults.

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

[73198ff](https://github.com/MetaMask/metamask-mobile/commit/73198ff6128dcb3f8d2b15c476042864a3a3cdb9)

[chloeYue]

LGTM

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

[github-actions]

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - skip-smart-e2e-selection label found

All E2E tests pre-selected.

View GitHub Actions results

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
15 value mismatches detected (expected — fixture represents an existing user).
View details

[sonarqubecloud]

Quality Gate passed

Issues
0 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