[CHORE]: Handle CDP commands larger than 100MiB

[camdecoster]

Description

Add handling of oversized-message. choreographer should transparently split CDP payloads that exceed Chrome's 100 MiB pipe buffer.

Why should this change be made?

This feature was added to Kaleido in plotly/Kaleido#442, but it had the unintended consequence of breaking serialization. This was due to the fact that the payload had to be measured before sending it to determine the size. The naive serialization (using orjson instead of PlotlyJSONEncoder) broke on a number of data structures. At any rate, chunking belongs where serialization and the wire already live.

Scope

• Add payload size check to choreographer during serialization
• If the size is greater than the limit (~100MiB), chunk the payload
• If the payload can't be chunked, raise an error
• If the size is under the limit, handle the call normally

Notes

• Chrome's kReceiveBufferSizeForDevTools is a hardcoded 100 * 1024 * 1024
• The new size limit becomes V8's max string length (~512 MB), since reassembly uses join('').
• The changes should be transparent to users
• The chunking code from fix: exporting a large figure hangs Kaleido#442 will need to be removed
• The Kaleido bug for this regression is being tracked in v1.3 serialization regression Kaleido#465

[camdecoster]

@ayjayt do you have any thoughts on this plan? It was your comment in the Kaleido PR that led me to starting work.