websocket broken connection not handled in live query server

[pash2048]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue Description

Parse live query not check broken WebSocket connection and close them and 'websocketTimeout' in 'LiveQueryServerOptions' not have any effect, we need to handle and close broken connection

Steps to reproduce

Start a live query server and then connect to those, for example, if we lose our connection(torn off WIFI or ...) we don't get any event with Parse.Cloud.onLiveQueryEvent and connection still open

Actual Outcome

if we unplug the ethernet cable or turn off mobile data or WIFI nothing happens and the parse server doesn't get it

Expected Outcome

Close connection after websocketTimeout then trigger an event onLiveQueryEvent

Environment

Server

• Parse Server version: 5.2.1
• Operating system: ubuntu-desktop 18.04
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local and Parspack cloud provider

Database

• System (MongoDB or Postgres): MongoDB
• Database version: 4.4.14
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): local

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): JavaScript
• SDK version: 3.4.2

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[pash2048]

Dear @mtrezza, I fix it and want to contribute but problem is that I don't have any idea about how can create a test to check it.
can you help me, please?

[mtrezza]

@pash2048 Sure! I suggest you create a pull request and link it to this issue, so we can take a look.