feat: get feature flag supports evaluating minimum required version

[sallem-consensys]

Description

While fetching feature flag value, flags that support minimum version will automatically validate if the version is supported

Changelog

CHANGELOG entry: null

Related issues

Fixes:
https://consensyssoftware.atlassian.net/browse/MCWP-177

Manual testing steps

Feature: automatcally check if minimum required version is supported for feature flag

  Scenario: user calls getFeatureFlag
    Given feature flag key

    When user calls getFeatureFlag
    Then the minimum version is automatically validated and a toast is thrown in non production environment if the version does not support the flag

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

Updates feature flag context to return raw values and auto-validate boolean-with-minimumVersion flags with a non-production toast on unsupported versions; adjusts UI type export and expands tests.

• Feature Flag Context (app/contexts/FeatureFlagOverrideContext.tsx):
  • getFeatureFlag now returns the raw flag value (or undefined) instead of FeatureFlagInfo.
  • Adds minimum version validation for boolean with minimumVersion flags via isMinimumRequiredVersionSupported; shows a Toast (non-production) and returns false if unsupported.
  • Integrates ToastContext and ToastVariants; introduces validateMinimumVersion helper.
• UI (app/components/Views/FeatureFlagOverride/FeatureFlagOverride.tsx):
  • Exports MinimumVersionFlagValue interface for shared typing.
• Tests (app/contexts/FeatureFlagOverrideContext.test.tsx):
  • Mocks Toast context; adds comprehensive tests for new getFeatureFlag behavior and version validation logic across environments.
  • Updates existing tests to expect raw values and new flag metadata access paths.

^{Written by Cursor Bugbot for commit e6e6945. 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.

[sonarqubecloud]

Quality Gate passed

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

[cursor]

Bug: Version Validation Fails in Production

The validateMinimumVersion function incorrectly returns flagValue.enabled for unsupported minimum versions in production. The version support check is currently coupled with the NODE_ENV condition, preventing it from returning false in production when a version is unsupported. This is contrary to test expectations, where version validation should apply regardless of environment.