test: refactors the e2e sh script to mjs for flakiness detection

[christopherferreira9]

Description

• Replace bash e2e runner with Node ESM.
• Add per-split duplication for new/modified specs to detect flakiness (base + 2 retries).
• Remove Octokit dependency; use native fetch + GitHub GraphQL.

What changed

• run-e2e-tags-gha.mjs: runs tests based on the Test Suite Tag passed on + ensures new and modified tests run 3 times to avoid the introduction of flaky tests

Behavior

• If skip-e2e-quality-gate label present: no test duplication.
• If no PR or no changed specs: no duplication.
• duplication only for ADDED/MODIFIED specs selected in the current split.

Testing
A new dummy test was added in order to showcase the spec file duplication.
Example logs from this run (no label applied and a new added test):

🚀 Running wallet-platform-android-smoke-2 tests on android
  Using TEST_SUITE_TAG: SmokeWalletPlatform
  🚀 Starting E2E tests...
  Running split 2 of 2
  Searching for tests with pattern: SmokeWalletPlatform
  Running split 2 of 2
  📋 Found 9 matching test files in total
  🧪 Duplicated for flakiness check: e2e/specs/multisrp/dummy-flakyness-retry-1.spec.ts
  🧪 Duplicated for flakiness check: e2e/specs/multisrp/dummy-flakyness-retry-2.spec.ts
  🧪 After duplication (per split), total selected files: 6
  🔍 Running 6 tests for split 2 of 2:
    - e2e/specs/multisrp/dummy-flakyness.spec.ts                 --> Original test file
    - e2e/specs/multisrp/dummy-flakyness-retry-1.spec.ts    --> Retry 1
    - e2e/specs/multisrp/dummy-flakyness-retry-2.spec.ts   --> Retry 2
    - e2e/specs/multisrp/export-srp-from-account-actions.spec.ts
    - e2e/specs/multisrp/export-srp-from-settings.spec.ts
    - e2e/specs/wallet/incoming-transactions.spec.ts
  🚀 Running matching tests for split 2...
  🤖 Running Android tests on GitHub Actions
  yarn run v1.22.22
  $ IS_TEST='true' NODE_OPTIONS='--experimental-vm-modules' detox test -c android.github_ci.release --headless --record-logs all e2e/specs/multisrp/dummy-flakyness.spec.ts e2e/specs/multisrp/dummy-flakyness-retry-1.spec.ts e2e/specs/multisrp/dummy-flakyness-retry-2.spec.ts e2e/specs/multisrp/export-srp-from-account-actions.spec.ts e2e/specs/multisrp/export-srp-from-settings.spec.ts e2e/specs/wallet/incoming-transactions.spec.ts

Example logs from this run (with label applied):

  🚀 Running wallet-platform-android-smoke-2 tests on android
  Using TEST_SUITE_TAG: SmokeWalletPlatform
  🚀 Starting E2E tests...
  Running split 2 of 2
  Searching for tests with pattern: SmokeWalletPlatform
  Running split 2 of 2
  📋 Found 9 matching test files in total
  ⏭️  skip-e2e-quality-gate detected; skipping flaky duplication
  🔍 Running 4 tests for split 2 of 2:
    - e2e/specs/multisrp/dummy-flakyness.spec.ts
    - e2e/specs/multisrp/export-srp-from-account-actions.spec.ts
    - e2e/specs/multisrp/export-srp-from-settings.spec.ts
    - e2e/specs/wallet/incoming-transactions.spec.ts
  🚀 Running matching tests for split 2...
  🤖 Running Android tests on GitHub Actions
  yarn run v1.22.22
  $ IS_TEST='true' NODE_OPTIONS='--experimental-vm-modules' detox test -c android.github_ci.release --headless --record-logs all e2e/specs/multisrp/dummy-flakyness.spec.ts e2e/specs/multisrp/export-srp-from-account-actions.spec.ts e2e/specs/multisrp/export-srp-from-settings.spec.ts e2e

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

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.

[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
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud