fix(data-drains): drain retryable response bodies in datadog/gcs loops

Mirrors the bigquery 401 fix. Without consuming the body before
sleeping, undici can't return the socket to the keep-alive pool, so
each retry leaks a TCP connection instead of reusing it.

Author: waleedlatif1

apps/sim/lib/data-drains/destinations/datadog.ts

@@ -179,6 +179,8 @@ async function postWithRetries(input: PostInput): Promise<Response> {
       }
       lastError = new Error(`Datadog responded with HTTP ${response.status}`)
       retryAfterMs = parseRetryAfter(response.headers.get('retry-after'))
+      /** Drain the retryable response body so undici can return the socket to the keep-alive pool. */
+      await response.text().catch(() => '')
     }
     if (attempt < MAX_ATTEMPTS) {
       await sleepUntilAborted(backoffWithJitter(attempt, retryAfterMs), input.signal)

apps/sim/lib/data-drains/destinations/gcs.ts

@@ -176,6 +176,8 @@ async function fetchWithRetry(input: RetryRequestInput): Promise<void> {
     }
     lastError = new Error(`GCS ${input.action} responded with HTTP ${response.status}`)
     const retryAfterMs = parseRetryAfter(response.headers.get('retry-after'))
+    /** Drain the retryable response body so undici can return the socket to the keep-alive pool. */
+    await response.text().catch(() => '')
     await sleepUntilAborted(backoffWithJitter(attempt, retryAfterMs), input.signal)
   }
   throw lastError instanceof Error