Description

Phase 3 analytics migration (Batch 3-17): migrate Sample Feature's components and hooks from useMetrics/MetricsEventBuilder to the new useAnalytics/AnalyticsEventBuilder analytics system.

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

Changes: SamplePetNamesForm, SampleCounterPane, and SampleFeatureDevSettingsEntryPoint now use useAnalytics() from app/components/hooks/useAnalytics/useAnalytics and createEventBuilder from the hook instead of useMetrics() and MetricsEventBuilder; test mocks updated to mock the useAnalytics hook with a chainable builder instead of useMetrics.

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MCWP-302 (Batch 3-17)

Manual testing steps

Feature: Sample Feature analytics

  Scenario: user triggers a Sample Feature flow event
    Given app is open and user is in a Sample Feature flow

    When user performs an action that triggers analytics (e.g. increment counter, add pet name, navigate to sample feature)
    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.