Restore does not fall back to gzip if zstd is present

[luk-lo]

When actions/cache/restore detects the presence of zstd on the path, it uses that to calculate the cache version it looks for. This leads to cache misses when the only available cache was created without zstd present.

In this case, the restore action should calculate the version again for gzip compression and try getting a cache with that version. When restore can handle both gzip and zstd compression, it should not limit the restorable cache version to only zstd.

[k-madejski]

@luk-lo same on our end, but you can try this workaround: apt-get update apt-get -y remove zstd

[Vampire]

I don't think issuing an apt-get will work on Windows where all runner images also have zstd, except for the new arm runners. ;-)

[Vampire]

The issue basically is a duplicate of https://github.com/actions/toolkit/issues/543 which I requested years ago already and that was rejected. :-(