refactor(analytics): C3-a migrate security, wallet UI, navigation, and settings to useAnalytics

[NicolasMassart]

Description

Part of the C3 analytics migration (#26686). This PR covers the navigation hook and global test setup cleanup.

What changed:

• useConnectionHandler.tsx: replaces useMetrics with useAnalytics — the tracked events (CONNECTION_DROPPED, CONNECTION_RESTORED) and navigation behaviour are unchanged
• useConnectionHandler.test.ts: updates mocks from useMetrics/MetricsEventBuilder to useAnalytics/AnalyticsEventBuilder using jest.mocked() and createMockUseAnalyticsHook
• testSetup.js: removes the global withAnalyticsAwareness HOC mock — the HOC is being deprecated and no longer needs a global stub

The rest of the original scope (TabBar, security/wallet UI components, Settings, Bridge) has been split into separate PRs for easier review by the respective code owners:

• #27983 — TabBar (@MetaMask/design-system-engineers)
• #27984 — Security/wallet UI components & Settings (@MetaMask/mobile-core-ux)
• #27985 — Bridge hook (@MetaMask/swaps-engineers)

Changelog

CHANGELOG entry: null

Related issues

Ref: #26814

Manual testing steps

N/A

Screenshots/Recordings

Before

N/A

After

N/A

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.

---

Note

Low Risk
Low risk refactor limited to analytics plumbing and Jest mocks; navigation timing and tracked event names remain the same.

Overview
Updates useConnectionHandler to call useAnalytics (instead of useMetrics) while keeping the same offline navigation timeout and emitting the same MetaMetricsEvents for connection dropped/restored.

Adjusts useConnectionHandler.test.ts to mock useAnalytics via createMockUseAnalyticsHook and to build assertions with AnalyticsEventBuilder, and removes the now-unneeded global withAnalyticsAwareness HOC mock from testSetup.js.

^{Written by Cursor Bugbot for commit 21fe914. This will update automatically on new commits. Configure here.}

[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.

[cursor]

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

There are 3 total unresolved issues (including 2 from previous reviews).

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

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
17 value mismatches detected (expected — fixture represents an existing user).
View details

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 90%

click to see 🤖 AI reasoning details

E2E Test Selection:
The changes are limited to the useConnectionHandler hook and its associated unit test and test setup. Specifically:

• Replaced useMetrics with useAnalytics hook.
• Updated event builder from MetricsEventBuilder to AnalyticsEventBuilder.
• Adjusted Jest mocks accordingly in unit tests and test setup.

This hook is responsible for handling connectivity changes and tracking analytics events (e.g., CONNECTION_DROPPED / CONNECTION_RESTORED) and optionally navigating to OfflineModeView. There are no changes to:

• Core Engine or Controllers
• Navigation structure or route names
• UI components or rendering logic
• Transaction, network, account, trade, card, perps, predictions, ramps, snaps, or multi-chain flows
• Performance-sensitive areas (rendering, startup, asset loading, swaps, onboarding)

The modification is an internal analytics hook swap with corresponding unit test updates. Since E2E tests do not validate analytics tracking internals and no user-facing behavior or navigation logic was altered, existing E2E flows should not be impacted.

Therefore, no E2E smoke tags are required for safe validation of this change.

Performance impact: None. The change only swaps analytics hook usage and test mocks, with no rendering, state management, or initialization changes. No performance tests are needed.

Performance Test Selection:
No UI, rendering, startup, network, asset loading, or critical user flow changes. The change is limited to analytics hook wiring and unit test mocks, with no measurable performance impact.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud