feat: 1653 first feature flag poc

[frankvonhoven]

Description

• This is the actual first implementation of the LaunchDarkly API for feature flags
• This utilizes the mobileMinimumVersions.appMinimumBuild feature flag in LaunchDarkly

Related issues

Fixes: #1653

This PR builds upon work in previous LD setup work: #10294

Manual testing steps

1. Start the app
2. in app/components/hooks/MinimumVersions/useMinimumVersions.tsx

• Change line: 22 featureFlags?.mobileMinimumVersions?.appMinimumBuild > currentBuildNumber;
  to: featureFlags?.mobileMinimumVersions?.appMinimumBuild > 0;

3. Restart app & enter password
4. Modal should popup prompting user to update app version

Screenshots/Recordings

Before

After

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2024-10-03.at.15.12.17.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.

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

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 70c9251
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b07260f5-e3e3-4f03-86c4-e493290719ad

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[NicolasMassart]

We need tests!

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 0099fc0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/022623a7-bb67-40d9-9ec1-741c41f4e4fa

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[NicolasMassart]

Simplify test name so they are easy to understand the use case. People hardly think in reverse.
Direct positive sentences are easier even if implementation requires an expect.not.to...

[tommasini]

LGTM! Aggree with Nico comments! let me know when resolved and I will approve it again

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
57.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 5dd76e9
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/747b0085-d0ea-4d1a-a299-4255c777dcb7

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise