Description

Phase 2 analytics migration (Batch 2-11): migrate Stake/Earn's useMetrics hook and MetaMetrics.getInstance() calls from the legacy MetaMetrics system to the new analytics system.

Reason: Deprecate MetaMetrics in favour of the shared analytics utility and AnalyticsController.

Changes: Stake components and hooks now use useAnalytics from hooks/useAnalytics/useAnalytics and import MetaMetricsEvents directly from core/Analytics; withMetaMetrics utility now uses analytics.trackEvent() and AnalyticsEventBuilder instead of MetaMetrics.getInstance().trackEvent() and MetricsEventBuilder; test mocks updated accordingly.

Changes

Source files (6):

• LearnMoreModalFooter.tsx, StakingButtons.tsx, StakingBalance.tsx, StakeButton/index.tsx: replaced useMetrics with useAnalytics; MetaMetricsEvents now imported from core/Analytics
• usePoolStakedDeposit/index.ts: replaced useMetrics with useAnalytics (also migrated as it's the source for a listed test file)
• withMetaMetrics.ts: replaced MetaMetrics.getInstance().trackEvent() with analytics.trackEvent() and MetricsEventBuilder with AnalyticsEventBuilder

Test files (3):

• StakeButton.test.tsx: replaced useMetrics mock with useAnalytics mock; added transitive useMetrics mock for unmigrated useStablecoinLendingRedirect dependency; replaced MetricsEventBuilder with AnalyticsEventBuilder
• usePoolStakedDeposit.test.tsx: replaced useMetrics mock/import with useAnalytics; replaced MetricsEventBuilder with AnalyticsEventBuilder
• withMetaMetrics.test.ts: replaced MetaMetrics.getInstance() spy with analytics module mock; updated MetaMetricsEvents import from core/Analytics

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MCWP-298 (Batch 2-11)

Manual testing steps

Feature: Stake/Earn analytics

  Scenario: user triggers a stake/earn flow event
    Given app is open and user is in a stake/earn flow

    When user performs an action that triggers analytics (e.g. stake button, unstake button, learn more, view staked positions)
    Then the event is tracked on Mixpanel

Screenshots/Recordings

N/A – analytics migration, no UI change.

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.