frontend: Stop NetworkSpeedTest reconnect interval multiply

[joaoantoniocardoso]

Summary

• Keep a single 200ms ping interval for the page lifetime.
• On disconnect, only recreate the WebSocket (do not nest another setInterval).

Test plan

• Open Tools → Network test, leave the page open with a flaky WS: interval count stays at one
• Latency updates while connected; reconnect recovers without runaway timers
• Leave the page: interval cleared, socket closed

[github-actions]

Automated PR Review

0. Summary

• Verdict: LGTM

Fixes a real interval-leak bug in NetworkSpeedTest.vue: the previous openWebSocket() created a fresh setInterval on every call, and since the interval itself invoked openWebSocket() to reconnect on drops, each disconnect nested another timer (200 ms → 100 ms → 50 ms → …). The PR moves the single interval to mounted() and reduces the renamed connectWebSocket() to socket setup only, with a defensive this.websocket?.close() before reassigning. Cleanup in beforeDestroy() still clears the (now single) interval. Also worth noting: the early return after connectWebSocket() inside the tick correctly avoids the InvalidStateError you'd otherwise get from send() on a CONNECTING socket.

No further comments, nice job 👍

Generated by PR Review Bot. This is advisory, a human reviewer must still approve.

[joaoantoniocardoso]

Superseded by #4045 (same changes, head moved to fork joaoantoniocardoso/BlueOS-docker).

[joaoantoniocardoso]

Closed in favor of #4045.