Fixed issue with big recording chunks

We resolved an issue where, while recording, oversized chunks (recording slices) were created by the browser, but, because of their size, they were refused by our ingestion servers. This caused the desktop recording client to fall into a re-connection loop and the oversized chunk and further chunks were never received by the server.

We implemented a new client side mechanism to split these huge chunks - that exceed the maximum size we accept on the ingestion server - into smaller pieces before sending them to our ingestion servers.

Generating such a large recording chunk was a very rare issue. Even though it happened on vanilla browsers (Chrome on Windows, Chrome on Andorid, etc.) we were only able to replicate it and find the root cause (a browser bug) on Safari on macOS/iOS.

le: we were also able to generate large chunks on:

1. Chrome on Android by locking the screen while recording: large chunk is generated when you unlock the phone
2. Chrome on macOS/Windows by entering sleep mode: large chunk is generated when you stop the recording

We also wrote a blog post on the subject.