Feature: Chunk single big transactions into multiple ones

[gdorsi]

We do currently throw an error when a transaction is too big to be stored, to avoid having issues with WebSockets limits.

To provide a better DX we should chunk them in smaller pieces, to ensure that any kind of change can be synced without issues.

[nrainhart]

Note: the chunking/reconstruction would be done at CoValueCore level, and on RawCoValues it would be visible as a single transaction.

[gdorsi]

Note: the chunking/reconstruction would be done at CoValueCore level, and on RawCoValues it would be visible as a single transaction.

Thinking about this more, it migh be even better to operate inside the WebSocket peer.
In the end we are trying to solve a transport issue, so the transport layer might be the right solution for the problem.

We could even downgrade this kind of content chunks as "low priority" so they won't congestion the network layer too much.