Adopt createUIQueryClient surface guards in extension UI

File: ui/contexts/query-client.ts, shared/constants/data-services.ts
Size: S | Hours: 2–3

Problem

PR #41183 wired createUIQueryClient into the extension but left DATA_SERVICES = []. Once the core-side guards for the QueryClient mutation surface ship (tier-1 and tier-2 bypasses for setQueryData, setQueryDefaults, fetchQuery, etc.), the extension needs to adopt them and verify end-to-end behavior.

Solution

After core guards land:

1. Upgrade @metamask/react-data-query in package.json.
2. Verify that the guards fire for a registered data-service key (e.g. queryClient.setQueryData(['SomeDataService:foo'], {...}) throws).
3. Audit the three Option C raw-TQ consumers (useHistoricalPrices, activity-v2/hooks, useMerklRewards) to confirm their keys don't accidentally overlap with any registered data-service prefix.
4. Document the key-prefix boundary in a comment near DATA_SERVICES.

Acceptance Criteria

• @metamask/react-data-query bumped to version containing the guards
• Runtime guard smoke-tested against a registered data service
• Option C consumers audited and confirmed non-overlapping
• Existing UI useQuery usages (wrapper + Option C) unchanged and still green

Dependencies

Depends on: MetaMask/core#8530 — QueryClient surface guards
Related: PR #41183

Start with ui/contexts/query-client.ts and shared/constants/data-services.ts, then inspect package.json for the @metamask/react-data-query version. After the core guards land, verify the registered-key smoke case, audit useHistoricalPrices, activity-v2/hooks, and useMerklRewards for prefix overlap, and document the boundary near DATA_SERVICES while keeping existing useQuery usage green.