test: fix unmatched mocked polymarket mocks

[cortisiko]

Description

Prevents Polymarket E2E tests from leaking live requests by adding a default gamma-api.polymarket.com/events/{id} mock response and ensuring it matches any numeric event id.

Updates the trending feed mock for event details to use the same generalized numeric-id matcher (instead of hard-coding /events/1), so prefetch/highlight flows don’t crash on unmatched ids.

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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

Low Risk
Low risk: changes are limited to E2E test mocks/fixtures and onboarding test flow, reducing flaky/unmocked network calls without touching production logic.

Overview
Prevents Polymarket E2E tests from leaking live requests by adding a default gamma-api.polymarket.com/events/{id} mock and broadening existing trending-feed event-detail mocks to match any numeric event id.

Updates onboarding E2E flows to proceed past the new OnboardingInterestQuestionnaire step when opting into MetaMetrics, adds a page-object wrapper for that screen, and seeds onboarding-fixture.json with a stable @MetaMask:AnalyticsId.

^{Reviewed by Cursor Bugbot for commit 91267e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.83%. Comparing base (3751d9a) to head (943ae9d).
⚠️ Report is 194 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #30194      +/-   ##
==========================================
+ Coverage   81.54%   81.83%   +0.28%     
==========================================
  Files        5343     5408      +65     
  Lines      142128   144344    +2216     
  Branches    32411    32967     +556     
==========================================
+ Hits       115899   118122    +2223     
+ Misses      18299    18139     -160     
- Partials     7930     8083     +153     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cortisiko]

@metamaskbot update-mobile-fixture

[github-actions]

🔄 Fixture update started. Running workflow from branch e2e/mock-pred-endpoints. View workflow runs

[github-actions]

❌ E2E fixture update failed.\n\nCommon causes:\n- CI workflow is still running — wait for 'Build iOS Apps' to complete\n- CI workflow was skipped — ensure your PR has iOS-impacting changes or use skip-smart-e2e-selection label\n- iOS build failed — check the CI workflow for errors\n\nView logs and retry

[github-actions]

❌ E2E fixture update failed.\n\nCommon causes:\n- CI workflow is still running — wait for 'Build iOS Apps' to complete\n- CI workflow was skipped — ensure your PR has iOS-impacting changes or use skip-smart-e2e-selection label\n- iOS build failed — check the CI workflow for errors\n\nView logs and retry

[cortisiko]

@metamaskbot update-mobile-fixture

[github-actions]

🔄 Fixture update started. Running workflow from branch e2e/mock-pred-endpoints. View workflow runs

[github-actions]

❌ E2E fixture update failed.\n\nCommon causes:\n- CI workflow is still running — wait for 'Build iOS Apps' to complete\n- CI workflow was skipped — ensure your PR has iOS-impacting changes or use skip-smart-e2e-selection label\n- iOS build failed — check the CI workflow for errors\n\nView logs and retry

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 502e0c3. Configure here.}

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeAccounts, SmokeConfirmations, SmokeIdentity, SmokeNetworkAbstractions, SmokeNetworkExpansion, SmokeSwap, SmokeStake, SmokeWalletPlatform, SmokeMoney, SmokePerps, SmokeMultiChainAPI, SmokePredictions, SmokeSeedlessOnboarding, SmokeBrowser, SmokeSnaps
• Selected Performance tags: @PerformanceAccountList, @PerformanceOnboarding, @PerformanceLogin, @PerformanceSwaps, @PerformanceLaunch, @PerformanceAssetLoading, @PerformancePredict, @PerformancePreps
• Risk Level: high
• AI Confidence: %

click to see 🤖 AI reasoning details

E2E Test Selection:
Fallback: AI analysis did not complete successfully. Running all tests.

Performance Test Selection:
Fallback: AI analysis did not complete successfully. Running all performance tests.

View GitHub Actions results

[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