SDK fails to handle TDF files where the content is compressed

[EmberPlot]

The SDK fails when the compression method used to store the manifest or the payload is not "STORE". This leads to incompatibilities with 3rd party implementations. Example:

$ unzip -v sample-deflate.ztdf
Archive:  sample-deflate.ztdf
 Length   Method    Size  Cmpr    Date    Time   CRC-32   Name
--------  ------  ------- ---- ---------- ----- --------  ----
    2467  Defl:N     1554  37% 04-02-2026 15:54 833b2d15  0.manifest.json
16131994  Defl:N   147723  99% 04-02-2026 13:09 29e7a099  0.payload
--------          -------  ---                            -------
16134461           149277  99%                            2 files
$ otdfctl inspect sample-deflate.ztdf
{
  "message": "not a valid TDF: file or input is not a valid TDF\njson.Unmarshal failed:invalid character '\\u008d' looking for beginning of value",
  "status": "ERROR"
}

[jrschumacher]

@EmberPlot we don't support compression as part of the specification.