Fix op compression when using an older loader

[andre4i]

Description

AB#3538

For loaders older than client_v2.0.0-internal.1.2.0 (exclusive), compression gracefully does not work (it does happen, but the messages are eventually sent uncompressed over the wire)

However, for loaders between client_v2.0.0-internal.1.2.0 (inclusive) and client_v2.0.0-internal.2.2.0 (exclusive), the runtime will provide the loader with the compression field as such:

this.params.containerContext.submitBatchFn(
                batch.content.map((message) => ({
                    contents: message.contents,
                    metadata: message.metadata,
                    compression: message.compression, // <-- compression marker
                    referenceSequenceNumber: message.referenceSequenceNumber,
                })),
                batch.referenceSequenceNumber,
            );

but the delta manager, on the loader side will ignore that field. Therefore, the message is sent over the wire without any compression markers. This means that no client is able to process this compressed message as it has no compression marker, and the container will close with assert 0x3ce (Runtime message of unknown type).

To work around this, the runtime must figure out if the message is compressed based on its 'shape'

This change also replaces the assert with an explicit data processing error.

[msfluid-bot]

⯅ @fluid-example/bundle-size-tests: +1.77 KB

Metric Name	Baseline Size	Compare Size	Size Diff
aqueduct.js	432.49 KB	433.37 KB	⯅ +907 Bytes
connectionState.js	680 Bytes	680 Bytes	■ No change
containerRuntime.js	227.59 KB	228.48 KB	⯅ +909 Bytes
loader.js	152.93 KB	152.93 KB	■ No change
map.js	43.78 KB	43.78 KB	■ No change
matrix.js	135.95 KB	135.95 KB	■ No change
odspDriver.js	91.79 KB	91.79 KB	■ No change
odspPrefetchSnapshot.js	43.51 KB	43.51 KB	■ No change
sharedString.js	156.5 KB	156.5 KB	■ No change
Total Size	1.36 MB	1.36 MB	⯅ +1.77 KB

---

Baseline commit: 1df94c8

Generated by 🚫 dangerJS against 7b3b79b