[John-David Dalton (jdalton)]

Make direct Socket API requests honor SOCKET_CLI_API_TIMEOUT, including redirects and stalled response bodies.

Local HTTPS tests cover timeouts, redirects, successful requests, and unset or invalid configuration.

Automated review notes

---

[!NOTE]
Medium Risk
Changes outbound API HTTP behavior for all configured-timeout CLI calls; misconfigured low timeouts could cut off legitimately slow responses, though unset/invalid config preserves prior no-deadline semantics for raw fetches.

Overview
Wires SOCKET_CLI_API_TIMEOUT into direct Socket API traffic so queryApi / sendApiRequest (GET and POST) honor a finite positive configured deadline, while invalid values are ignored via resolveConfiguredSocketApiTimeout.

apiFetch gains an optional timeout on the underlying https.request: when set, the client destroys the request on timeout (ETIMEDOUT), propagates that through redirects, and surfaces it on aborted idle response bodies. The global API timeout is not auto-applied to bare apiFetch calls—only explicit timeout on those—so unset config still allows slow/streaming responses.

Adds unit tests for timeout resolution and a local HTTPS integration suite (with test certs) covering GET/POST failures, idle-body abort, success within limit, unset config, raw fetch behavior, and 302/307 redirects.

^{Reviewed by Cursor Bugbot for commit 83a3038. Configure here.}

[mikeraymonf13-creator]

👀