Turn on the new WebSocket implementation by default.

LayoutTests/virtual/stable/http/tests/websocket/invalid-encode-length-expected.txt

Index: LayoutTests/virtual/stable/http/tests/websocket/invalid-encode-length-expected.txt
diff --git a/LayoutTests/virtual/stable/http/tests/websocket/invalid-encode-length-expected.txt b/LayoutTests/virtual/stable/http/tests/websocket/invalid-encode-length-expected.txt
deleted file mode 100644
index b6deae5782ba299267f29d643cbe833e0ab2e29a..0000000000000000000000000000000000000000
--- a/LayoutTests/virtual/stable/http/tests/websocket/invalid-encode-length-expected.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-encode-length?case=126_125' failed: The minimal number of bytes MUST be used to encode the length
-CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-encode-length?case=126_0' failed: The minimal number of bytes MUST be used to encode the length
-CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-encode-length?case=127_65535' failed: The minimal number of bytes MUST be used to encode the length
-CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-encode-length?case=127_0' failed: The minimal number of bytes MUST be used to encode the length
-Test whether WebSocket aborts the connection when it receives an unexpected encoding length frame.
-
-On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-
-Case 126_125: Test started.
-onopen() was called.
-onclose() was called.
-PASS closeEvent.wasClean is false
-Case 126_0: Test started.
-onopen() was called.
-onclose() was called.
-PASS closeEvent.wasClean is false
-Case 127_65535: Test started.
-onopen() was called.
-onclose() was called.
-PASS closeEvent.wasClean is false
-Case 127_0: Test started.
-onopen() was called.
-onclose() was called.
-PASS closeEvent.wasClean is false
-PASS successfullyParsed is true
-
-TEST COMPLETE
-