Utility.Networking.WebSocketException: Exception of type 'Utility.Networking.WebSocketException' was thrown.

Sentry Issue: [UNITY-EXPLORER-Q50](https://decentraland.sentry.io/issues/7725792918/)

```
Utility.Networking.WebSocketException: Exception of type 'Utility.Networking.WebSocketException' was thrown.
File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/Utility/Networking/DCLWebSocket.cs", line 99, in ReceiveAsync
File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/CrdtEcsBridge/JsModulesImplementation/ClientWebSocketApiImplementation.cs", line 250, in ReceiveAsync
File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/Utility/Networking/DCLWebSocket.cs", line 99, in ReceiveAsync
File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/CrdtEcsBridge/JsModulesImplementation/ClientWebSocketApiImplementation.cs", line 118, in ReceiveAsync
File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/CrdtEcsBridge/JsModulesImplementation/ClientWebSocketApiImplementation.cs", line 274, in ReceiveAsync
...
(245 additional frame(s) were not displayed)
```
This issue was automatically created by Sentry via [Explorer Alpha Github Issue Creation](https://sentry.io/organizations/decentraland/monitors/alerts/3130340/)

Start with Assets/DCL/Infrastructure/Utility/Networking/DCLWebSocket.cs at ReceiveAsync line 99, then trace the calls in ClientWebSocketApiImplementation.cs at the reported lines. Use the Sentry stack trace to understand the failing receive path and look for a reproducible scenario. Done means identifying and fixing the cause of the WebSocketException, with coverage or verification for the affected receive flow.

Written by the indexing model from the issue text.