E2E Test Selection:
The PR removes the marginDeployed field from the Perps Trading Campaign feature across multiple layers:

1. RewardsController.ts (critical): Removes marginDeployed from the leaderboard position cache read/write paths. This is a narrow, focused change to a critical controller - only 2 lines removed.

2. types.ts (critical): Removes marginDeployed from PerpsTradingCampaignLeaderboardPositionDto and PerpsTradingCampaignLeaderboardPositionFoundState. Also updates the qualified field comment to reflect that only notional volume ≥ $25k is required (margin requirement removed).

3. UI Components: PerpsTradingCampaignStatsView.tsx and PerpsCampaignStatsSummary.tsx both remove the "Margin" stat cell from their respective UIs, restructuring the layout.

4. Localization: All 15 language files remove label_margin and label_margin_deployed keys.

5. Unit tests: Updated to reflect the removal.

Tag Selection Rationale:

• SmokePerps: Directly tests Perps functionality including the Add Funds flow and Perps interface. The campaign stats view changes (removing margin display) are part of the Perps UI that these tests exercise. The RewardsController changes affect the data layer for Perps campaigns.
• SmokeWalletPlatform: Per the tag description, Perps is a section inside the Trending tab, and changes to Perps views (headers, lists, full views) affect this tag. The PerpsTradingCampaignStatsView and PerpsCampaignStatsSummary are Perps views embedded in Trending.

No E2E tests directly test marginDeployed or the campaign stats view specifically - these are covered by unit tests. The changes are backward-compatible removals that simplify the UI. The RewardsController change is narrow and doesn't affect core authentication, opt-in, or subscription flows.

Performance Test Selection:
The changes remove a single field (marginDeployed) from the Perps campaign leaderboard position data and its UI display. This is a data model simplification with no impact on rendering performance, list rendering, data loading patterns, or critical user flows. No performance-sensitive code paths are affected.