HTTP calls from components lack observability

[betterclever]

Problem

API wrapper components (like AbuseIPDB, VirusTotal) and the HTTP Request component make external HTTP calls, but the traces provide very limited visibility into what actually happened:

• No request details - Can't see the exact URL, headers, or body that was sent
• No response details - Can't inspect response headers or body content
• No timing breakdown - No visibility into DNS, connect, TLS handshake, or TTFB
• Hard to debug - When an API call fails, users have to guess what went wrong
• No way to reproduce - Can't easily copy the request to test in Postman/cURL

Current State

When viewing a workflow trace, HTTP-based components only show:
```
NODE_STARTED: abuseipdb-check
NODE_PROGRESS: Checking IP: 1.1.1.1
NODE_COMPLETED: { ... output ... }
```

Users have no idea what HTTP request was actually made or what the API returned.

Expected Behavior

Traces should capture full HTTP exchange details:

• Request: method, URL, headers (with secrets masked), body
• Response: status, headers, body preview
• Timing: total duration and phase breakdown
• Export: ability to get cURL command or HAR file

Acceptance Criteria

• New trace event types for HTTP request/response
• Instrumented fetch wrapper in component SDK
• Automatic secret masking for sensitive headers
• Timing capture via Undici diagnostics (Node.js)
• HAR-compatible data format
• Migration of existing HTTP components