feat: sentry error monitoring for quick buy and top traders

[Bigshmow]

Description

Adds feature:social Sentry error instrumentation for Top Traders and Quick Buy, following existing Logger.error` + tags pattern.

• New helpers in socialServiceTelemetry.ts: buildSocialLoggerErrorOptions, formatSocialExtraMessage, SOCIAL_SENTRY_FEATURE
• Top Traders: leaderboard fetch/refresh + pull-to-refresh (useTopTraders, TopTradersView)
• Quick Buy: quote fetch + submit tx (useQuickBuyQuotes, useQuickBuyBottomSheet)
• more WIP...

Events are sent via existing Logger.error > Sentry on release builds (metrics opt-in, DSN). Search in Sentry: feature:social, surface:top_traders, surface:quick_buy.
Sentry alert rules (Slack/email on feature:social) are out of scope for this PR and will be configured separately.

Out of scope (follow-up)

• feature:ai for digests / market insights

Changelog

CHANGELOG entry: null

Related issues

Resolves: TSA-150

Manual testing steps

• yarn jest app/util/social/socialServiceTelemetry.test.ts
• yarn jest on useTopTraders.test.ts, TopTradersView.test.tsx
• Verify events in Sentry after release/internal build (not Metro dev — Logger.error no-ops in __DEV__)

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
Changes are limited to error logging and test expectations; user flows and API behavior are unchanged aside from Quick Buy failures now going through Logger/Sentry instead of console.

Overview
Standardizes Social failures for Sentry with a shared feature:social tagging model in socialServiceTelemetry.ts, aligned with existing Perps-style Logger.error options.

Telemetry helpers: Adds buildSocialLoggerErrorOptions, reportSocialServiceFailure, useLogSocialQueryError, and formatSocialQueryErrorMessage; renames legacyMessage → extraMessage in buildSocialErrorExtras; extends surfaces/endpoints (e.g. trader_profile, follow/unfollow, Quick Buy without a SocialService endpoint).

Call-site migration: Social react-query hooks (useTopTraders, useFollowedTraders, useTraderProfile, useTraderPositions, useTraderPosition) drop per-hook useEffect logging in favor of useLogSocialQueryError + structured refresh failures. Quick Buy replaces console.error with Logger.error on quote fetch and tx submit (chain tags). Top Traders pull-to-refresh and follow/unfollow use the same structured payload. Tests assert tags/extras instead of plain string second arguments.

^{Reviewed by Cursor Bugbot for commit d1fa812. Bugbot is set up for automated code reviews on this repo. 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.

[github-actions]

🔍 Smart E2E Test Selection

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

click to see 🤖 AI reasoning details

E2E Test Selection:
All 20 changed files are Social Leaderboard feature files (hooks, telemetry utilities, and their unit tests). The changes are purely a telemetry/error-logging refactor: replacing scattered Logger.error + useEffect patterns with centralized helpers (reportSocialServiceFailure, useLogSocialQueryError, formatSocialQueryErrorMessage, buildSocialLoggerErrorOptions). No business logic, UI rendering, API calls, or data flows were changed. The Social Leaderboard (Top Traders, Trader Profile, Trader Position, Quick Buy, Followed Traders) is embedded in the Trending tab, which is tested under SmokeWalletPlatform. Since there are no dedicated E2E tests for Social Leaderboard and the changes are low-risk internal refactors, SmokeWalletPlatform is the most relevant tag to validate the Trending/Social surfaces still function correctly. No other tags are warranted as the changes don't touch confirmations, accounts, networks, swaps, snaps, or any other feature area.

Performance Test Selection:
The changes are purely telemetry/error-logging refactors with no impact on rendering performance, data loading, UI components, or critical user flows. No performance-sensitive code paths were modified.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud