[Issue/3320] Prevent WebSocketConnection burst of exceptions when connection fails

[gabrielbeamable]

Ticket

resolves #3320

Brief Description

Our retry logic for the Unity SDK WebSocket was not delayed, but rather always immediately trying to connect again, which was leading to an infinite spam of errors in the console. Now we are waiting for some time before trying again to connect, in the following sequence of delays:

• Starts trying immediately
• If fails again, then it increments a delay for retrying the connection, which follows the sequence:
  • 1, 2, 4, 8, 16, 32, 60, 60, 60 ... (seconds)

Checklist

• [x] Have you added appropriate text to the CHANGELOG.md files?

Notes

When you are merging a feature branch into main, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging from main to staging, or staging to production, please use a regular merge commit.

Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?

[allister-beamable]

looks like a compiler error in 2020

-----EndCompilerOutput---------------
- Finished script compilation in 29.863052 seconds
Packages/com.beamable/Runtime/Connection/WebSocketConnection.cs(164,21): error CS0117: 'Math' does not contain a definition for 'Clamp'

Oof! Who doesn't include Clamp in their math lib? Rough.