Hotfix Zstd breaking due to version change in runners

[lvpx]

Summary

Currently zstd check is dependent on the text output of the zstd --version to include zstd command line interface. This text changed to *** Zstandard CLI (64-bit) v1.5.4, by Yann Collet *** breaking the check and @actions/cache always falling back to gzip compression.

Implementation

• Set to use gzip if the version output string is empty which should be the case if zstd is not installed.
• Introduced --quiet flag to zstd so moving on the zstd --version should output machine readable version parsable via SemVer instead of text.
• Removed code that checks for version less than 1.3.2 as it was not working. Now we default to using zstd without --long as that is what currently happens.

Next Steps

Will have another PR that fixes use of zstd with --long as intended. This release should unblock zstd usage.

Issues

Fixes #1341

[bishal-pdMSFT]

Checks are failing. Please fix the unit tests.

[cdce8p]

Thanks again @pdotl!

Just saw this while looking at the PR. '${app}' seems a bit redundant. The first argument should be a string and app is already one. Maybe you can fix that when you address the zstd --long issue. It would be a bit much to open a separate PR for it 😅

[lvpx]

Sure @cdce8p will take this up in the next PR.

[Phantsure]

Looks fine to remove --long check entirely. --quiet would supress warnings but not clear how that would help in semver readable text

[cdce8p]

--quiet would supress warnings but not clear how that would help in semver readable text

Found this in the documentation for zstd

V, --version: display version number and exit. Advanced : -vV also displays supported formats. -vvV also displays POSIX support. -q will only display the version number, suitable for machine reading.