[Due for payment 2025-02-13] [Due for payment 2025-02-10] Pusher PingPong is making clients go offline too often

[tgolen]

Problem

Once the pusher pingpong was implemented in #55326, it's resulted in more clients being forced offline than I had expected. This prevents users from using the app.

Solution

Turn off the portion of the ping-pong that forces clients to go offline when the PONG event is not received and analyze the logs to see what behavior is happening with the ping-pong so it can be dialed in better.

[melvin-bot]

Triggered auto assignment to @yuwenmemon (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.93-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [No QA] [CP Staging] Disable the network going offline for now when a PONG is not received #56183

If no regressions arise, payment will be issued on 2025-02-10. 🎊

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.94-25 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [No QA] [CP Staging] Disable the network going offline for now when a PONG is not received #56183

If no regressions arise, payment will be issued on 2025-02-13. 🎊