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

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

```
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 84, in ReceiveAsync
File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/CrdtEcsBridge/JsModulesImplementation/ClientWebSocketApiImplementation.cs", line 244, in ReceiveAsync
File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/Utility/Networking/DCLWebSocket.cs", line 84, in ReceiveAsync
File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/CrdtEcsBridge/JsModulesImplementation/ClientWebSocketApiImplementation.cs", line 112, in ReceiveAsync
File "C:/workspace/workspace/p/Explorer/Assets/DCL/Infrastructure/CrdtEcsBridge/JsModulesImplementation/ClientWebSocketApiImplementation.cs", line 268, 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 by reading DCLWebSocket.cs at line 84 and trace the ReceiveAsync calls in ClientWebSocketApiImplementation.cs at lines 112, 244, and 268. Use the Sentry issue and its stack trace to determine the triggering WebSocket condition and reproduce it if possible. Done means the underlying cause is addressed and the reported exception no longer occurs in that scenario.

Written by the indexing model from the issue text.