E2E Test Selection:
The PR introduces a new useAccountNoFundsAlert hook that creates a blocking "Danger" severity alert for moneyAccountDeposit transactions when the selected account has no available tokens. This replaces an inline text display in custom-amount-info.tsx with a proper alert system integration.

Key changes:

1. New useAccountNoFundsAlert hook - blocking alert for moneyAccountDeposit with no tokens
2. usePendingAmountAlerts - integrates the new alert into the pending amount alerts pipeline
3. custom-amount-info.tsx - removes inline "no funds" text (now handled by alert system)
4. alerts.ts - adds AccountNoFunds enum value
5. useConfirmationAlertMetrics.ts - maps new alert to analytics
6. en.json - adds new alert string, removes old inline string

Tag selection reasoning:

• SmokeConfirmations: Core change is to the confirmation alert system - new blocking alert type, alert key, metrics mapping. Any confirmation flow could be affected by alert system changes.
• SmokePerps: moneyAccountDeposit is the transaction type used in Perps Add Funds flow. The new blocking alert directly affects this flow when account has no funds. Per tag description, SmokePerps requires SmokeConfirmations.
• SmokeWalletPlatform: Required by SmokePerps tag description (Perps is a section inside Trending tab).
• SmokeCard: Card's Add Funds feature uses deposit flows that could involve moneyAccountDeposit transactions. The blocking alert would affect this flow.
• SmokeTrade: Required by SmokeCard tag description (Add Funds uses swaps which require SmokeTrade).

The change is medium risk - it modifies the alert system for a specific transaction type (moneyAccountDeposit) and could affect user flows in Perps and Card features if the alert incorrectly blocks or fails to block transactions.

Performance Test Selection:
The changes are focused on alert logic and UI text replacement in the confirmation flow. No performance-sensitive code paths are modified - no list rendering, no data loading, no state management changes, no app startup code. The new hook uses useMemo appropriately and is lightweight. No performance tests are warranted.