CLDSRV-918: experiment - disable SDK request timeout

Comparison branch for the 10x flakiness measurement: identical to
bugfix/CLDSRV-918-raise-test-request-timeout except requestTimeout is 0
instead of 30000, to compare stale-socket-timer reset rates.

Author: tcarmet

tests/functional/aws-node-sdk/test/support/config.js

@@ -26,9 +26,12 @@ const DEFAULT_GLOBAL_OPTIONS = {
 // 120s; the v3 migration introduced a 5s timeout that heavy server-side
 // operations (multi-megabyte UploadPartCopy, 1000-key batch deletes) exceed
 // under CI load, as the server sends no response bytes until they complete.
-// 30s stays below mocha's 40s global timeout so a genuine hang still
-// surfaces as the SDK TimeoutError rather than a generic mocha timeout.
-const REQUEST_TIMEOUT = 30000;
+// 0 disables the SDK timeout entirely; mocha's 40s global timeout remains
+// the backstop for genuine hangs. Do not set a value of 6000 or more:
+// @smithy/node-http-handler then attaches the timer directly to pooled
+// keepAlive sockets without cleanup, and the stale timers destroy
+// connections out from under later requests.
+const REQUEST_TIMEOUT = 0;
 
 const DEFAULT_MEM_OPTIONS = {
     endpoint: `${transport}://127.0.0.1:8000`,