Make compression algorithm for `sysand build` configurable

[vytautas-astrauskas-sensmetry]

ZIP format supports multiple compression algorithms. We should enable users to choose which compression algorithm to use when building a KPAR with sysand build.

Note: We have to be careful with changing the default because different tools and libraries support different compression algorithms and we want to interoperate with as many tools as possible.

Subtasks:

• Add a configuration option.
• Add a test that round trips for all compression formats allowed by ZIPs to ensure that Sysand is able to read all possible ZIPs.

[daumantas-kavolis-sensmetry]

AFAIK Windows can only extract deflated zips by default (zipfile.ZIP_DEFLATED in Python). Additionally, having .kpar potentially mean one of many compressions algorithms would be just confusing. Different compression algorithms have different default file suffixes so I do not think this feature is necessary or warranted. SysML is already confusing enough as is.

Otherwise, is there any other package manager that allows mixing compression algorithms like here?

[andrius-puksta-sensmetry]

AFAIK Windows can only extract deflated zips by default

Windows 11 now uses libarchive (see section "File Explorer") and so can extract many more zip compression methods, including notably zstd/lzma/bzip2 (though they don't say anything about zip compression methods specifically).

[daumantas-kavolis-sensmetry]

Windows 11 now uses libarchive (see section "File Explorer") and so can extract many more zip compression methods, including notably zstd/lzma/bzip2 (though they don't say anything about zip compression methods specifically).

Not everyone is on the latest Windows. It will take multiple years for everyone to catch up.

[Jonas-Puksta-Sensmetry]

Implemented by #186