Description

Updates the onboarding interest questionnaire (“What do you want to do with MetaMask?”) to match the TMCU-792 design refresh:

• Options are shown in a two-column grid with consistent 8px gutters (50% column wrappers + padding).
• Each card uses a top-right selection indicator and keeps the existing option illustrations in app/images/.
• Copy updates in en.json: “Buy and sell crypto tokens” and “Trade perpetuals” (advanced_trades id unchanged for analytics).
• Continue still calls onComplete() directly (crypto experience screen is TMCU-833, separate PR).

Changelog

CHANGELOG entry: Updated the onboarding interest questionnaire layout to a two-column grid with refreshed option labels.

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/TMCU-792

Manual testing steps

Feature: Onboarding interest questionnaire grid (TMCU-792)

  Scenario: user completes interest questionnaire after opting in to metrics
    Given the user is on the OptinMetrics screen during onboarding
    And the interest questionnaire eligibility check returns true

    When the user opts in to basic usage data and taps Continue
    Then the interest questionnaire is shown with six options in a two-column grid
    And the user can select multiple options
    And tapping Continue submits analytics and proceeds with onboarding (onComplete)

  Scenario: user can skip selecting interests
    Given the user is on the interest questionnaire screen

    When the user taps Continue without selecting any option
    Then onboarding continues with skipped interest analytics

Screenshots/Recordings

Before

Light Mode	Dark Mode

After

Light Mode	Dark Mode

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.