Fix delay in websocket closed tests

The WenSocket web_tests
connect-error-by-no-websocket-server-closeonclose.html
connect-error-by-no-websocket-server-closeonerror.html
connect-error-by-no-websocket-server-noclose.html have been failing on
Windows 10 1909. In this version of Windows the delay on connecting to a
closed localhost port has increased from 1 second to 3 seconds. Adjust
the timeout in the tests to match.

BUG=1132194

Change-Id: I11b69ea3ed15daa9ab9dff2ce22672c706867da2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2483717
Commit-Queue: Yoichi Osato <yoichio@chromium.org>
Auto-Submit: Adam Rice <ricea@chromium.org>
Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#818353}

third_party/blink/web_tests/http/tests/websocket/resources/connect-error-by-no-websocket-server.js

@@ -53,9 +53,9 @@ function doTest(port, closeOnError, closeOnClose)
         }
     };
 
-    // Each failure to connect to 127.0.0.1 takes 1 second on Windows.
-    // Allow 2 seconds for padding.
-    timeoutID = setTimeout(timeOutCallback, 2000);
+    // Each failure to connect to 127.0.0.1 takes 3 seconds on Windows.
+    // Allow 4 seconds for padding.
+    timeoutID = setTimeout(timeOutCallback, 4000);
 }
 
 function timeOutCallback()