[browser][websocket][tests] WebSocket Abort tests multiple failures

[kjpou1]

There are multiple failures with the Abort tests causing some tests to:

• Never end

• Multiple GC calls that end in running out of memory.

• Some failures are expected to fail with specific WebSocketError codes:

Error codes that are not correct tend to be when websockets tests are looking for specific error codes and messages when the browser returns NativeError and the websocket native error code instead.

failed: WebSocket is closed before the connection is established.

These need to be marked correctly and or caught and wrapped correctly.

Assert.Equal() Failure
  info: Expected: Aborted
  info: Actual:   Closed

Other issues stem from the Abort being called before the connection. This depends on the modifications from PR #44722 being accepted.

Fixes for these should also fix some, note not all, of the memory runtime errors as per issue: #45586

Associate PR's: #44666 and #45470

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

There are multiple failures with the Abort tests causing some tests to:

• Never end

• Multiple GC calls that end in running out of memory.

• Some failures are expected to fail with specific WebSocketError codes:

Error codes that are not correct tend to be when websockets are looking for specific error codes and messages when the browser returns NativeError and the websocket native error code instead instead.

These need to be marked correctly and or wrapped caught and wrapped correctly.

Other issues stem from the Abort being called before the connection. This depends on the modifications from PR #44722 being accepted.

Fixes for these should also fix some of the memory runtime errors as per issue: #45586

Author:	kjpou1
Assignees:	kjpou1
Labels:	arch-wasm, area-System.Net
Milestone:	-