fix(WebSocketShard): Zombie connection fix

[legendhimself]

Fixes #8486, fixes #8984 and supersedes #8981

• Fix backport feat: backport handle zombie connection #7626 missing changes
• Reverted the pull request fix(WebSocketShard): either start close timeout or emit destroyed but never both #8956
• Removed unref of wsCloseTimeout
• We are resuming the connection for zombie instead of starting a new To not mess it up we didn't push this. Will create a separate pr for this.

Please describe the changes this PR makes and why it should be merged:

Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Comments	Updated
discord-js	⬜️ Ignored (Inspect)			Dec 31, 2022 at 4:02AM (UTC)
discord-js-guide	⬜️ Ignored (Inspect)			Dec 31, 2022 at 4:02AM (UTC)

[legendhimself]

Previous Report

Before the uptime was kind of bad thanks to the unref that we had on the WsCloseTimeout,

Current Report

The logs/tests proved reduced reconnects and better uptime at least on my 60+ Shards bot.
@DraftProducts Also has tested the changes on his bot with 350+ shards which had frequent zombie connections and most of the time ran out of logins per day. He will write more details soon on this pr.

Also thanks @shoxcy for providing me with shawarma during the testings

[kyranet]

Blocking for 2 days at @legendhimself's request so they can test the PR for more time. Will unblock afterwards.

[DraftProducts]

For now, I have excellent results.
Previously I was loosing multiple starts bucket tokens each 5 mins that brought me to multiple bot's token resets per day (3 to 5 times with 2000 bucket logins), had zombies connections and offline status bot on others.
I didn't notice any re-login or zombie connections since 2am when I merged our fix in production.

[DraftProducts]

I hear that you were waiting for more information, here are my session_start_limit remaining logins of the GET /bot/gateway request (without any token reset today).

{
  "url": "wss://gateway.discord.gg",
  "shards": 368,
  "session_start_limit": {
  	"total": 2000,
  	"remaining": 1995,
  	"reset_after": 79901986,
  	"max_concurrency": 16
  }
}

That shows that we just used 5 relogins today without any zombie connection, so for me the problem is solved, and this PR should be merged as soon as possible for others devs 🎉

[legendhimself]

Day 2,

Logins today

Stats Report

Uptime ^, No restarts so far. Usually, some of the shards by this time used to silently restart due to the unref on the closetimeout but now, as you saw in the previous login, everything is going fine with this fix.

This pr is safe to be merged unless someone else wants to test the fixes first. I think we can get this pr unblocked now and get it merged.

[iCrawl]

Looking good