Invalidate Linux build caches more agressively (#8031)

We run Linux CI on regular GitHub Action runners, which have ~30GB of
disk space. This is nothing for Rust builds and, due to Cargo.lock
perturbations, we tend to accumulate enough artifacts to fill the disk
entirely since `restore-keys` alowed to keep the cache for different
lockfiles.

Instead, try to invalidate the cache more aggressively (which will cost
us more frequent ~30min Linux CI runs) to see how this will work in
comparison.

Release Notes:

- N/A
37f6a706ccKirill Bulatov committed on 2/19/2024, 10:16:39 PM· committed by GitHubparentf4bafd5
1 file changedLine totals unavailable