Compact network dump output for long React Native flows

## Problem

`network dump` can burn thousands of tokens on opaque URLs, heartbeat/poll endpoints, and large Pusher JSON payloads during long React Native flows such as New Expensify expense creation.

## Desired behavior

Make default network output compact and useful, with explicit flags for full detail.

## Acceptance criteria

- Default `network dump` truncates or redacts opaque long query params.
- Heartbeat/poll endpoints are filtered or summarized by default.
- Pusher `multipleEvents` payloads summarize event count, first action/type, relevant keys, and timing when possible.
- Full URLs/noise/detail remain available behind explicit include flags or modes.
- Existing `summary|headers|body|all` behavior remains compatible or has a clear migration path.

## Testing

Unit/fixture:
- Expensify-shaped `/api/fl?...` fixture.
- Pusher `multipleEvents` fixture.
- Heartbeat/poll endpoint fixture.
- Explicit full-detail mode preserves raw URL/payload data.

New Expensify Android verification:
- Run the camera-scan expense flow with log markers.
- Run `network dump` and confirm output is compact but still identifies relevant create/IOU/Pusher activity.
- Confirm full-detail mode can still expose the raw request data when intentionally requested.

Inizia dal comando `network dump` e segui la gestione esistente di `summary|headers|body|all`. Esegui o aggiungi i fixture con struttura Expensify, Pusher `multipleEvents` e heartbeat/poll, quindi verifica l'output compatto predefinito e i dati grezzi nella modalità esplicita di dettaglio completo. La verifica Android utilizza il flusso delle spese con scansione tramite fotocamera di New Expensify e i relativi marker di log.

Scritto dal modello di indicizzazione a partire dal testo della issue.