[browser][ws] fix ConnectAsync_CancellationRequestedInflightConnect_ThrowsOperationCanceledException

[pavelsavara]

Fixes #97092

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Fixes #97092

Author:	pavelsavara
Assignees:	pavelsavara
Labels:	arch-wasm, area-System.Runtime.InteropServices.JavaScript, os-browser
Milestone:	9.0.0

[pavelsavara]

I'm really confused how this could happen.

Log

[15:05:50] info: [STRT] System.Net.WebSockets.Client.Tests.HttpClientConnectTest.ConnectAsync_CancellationRequestedBeforeConnect_ThrowsOperationCanceledException
[15:05:50] fail: [out of order message from the browser]: http://127.0.0.1:42619/_framework/dotnet.runtime.js 2 WebSocket connection to 'ws://38c12b6832644ebbbcc2f28974617f84/' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
[15:05:50] warn: [0x000dc23c 15:05:50.656] MONO_WASM: WebSocket error
[15:05:50] info: [STRT] System.Net.WebSockets.Client.Tests.HttpClientConnectTest.ConnectAsync_PassNoSubProtocol_ServerRequires_ThrowsWebSocketException(server: ws://127.0.0.1:42619/WebSocket/EchoWebSocket.ashx)
[15:05:50] warn: [0x000dc23c 15:05:50.667] MONO_WASM: WebSocket error
[15:05:50] fail: [0x000dc23c 15:05:50.668] MONO_WASM: Unhandled error: {}
[15:05:50] fail: [0x000dc23c 15:05:50.669] MONO_WASM: {"status":1,"silent":true}
[15:05:50] fail: [out of order message from the browser]: http://127.0.0.1:42619/_framework/dotnet.runtime.js 2 WebSocket connection to 'ws://127.0.0.1:42619/WebSocket/EchoWebSocket.ashx?subprotocol=CustomProtocol' failed: Error during WebSocket handshake: Response must not include 'Sec-WebSocket-Protocol' header if not present in request: CustomProtocol
[15:05:50] info: WASM EXIT 1

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).