Console-web stops receiving logs via websocket

Why

bug

Steps to reproduce

1. Open https://console-api-sandbox.akash.network/ deployment in https://console.akash.network/
2. Open logs
3. Wait 3-5 minutes, ensure that logs are not generated by somebody else, so websocket remains silent for some time
4. Send request to https://console-api-sandbox.akash.network/status via curl or just open in new browser tab to generate log entry
5. Observe the result in logs

Expected result

✅ new log entry shown

Actual result

❌ logs list is not updated

Observations

It seems that websocket connection is closed when it nothing goes through it, I see a successful attempt to reconnect but provider websocket connection on proxy is not established until client sends the 1st message and the code in DeploymentLogs.tsx does not do it. Once it establishes connection once, it then ignores attempts to send a message to websocket -> https://github.com/akash-network/console/blob/main/apps/deploy-web/src/components/deployments/DeploymentLogs.tsx#L120

Start at apps/deploy-web/src/components/deployments/DeploymentLogs.tsx around line 120 and reproduce the idle-connection sequence described in the issue. Inspect the reconnect and websocket message flow, then verify that after several minutes without logs, a newly generated log entry still appears in the logs list.