Use cache@v4 and save-always option

[kruszczynski]

Cheers lovely people of rainforest!

TLDR

Use github's cache action and it's save-always option instead of a fork that still uses node 16.

Long story

So I noticed a Node 16 warning when running my RF suite

I checked out always-upload-cache action but it seems neglected. I started looking into Github's cache action issue linked in its README and noticed that the v4 Changelog mentions a save-always option.

While it's not documented a quick peek the code suggests it does exactly what always-upload-cache does.

I haven't tested that yet, I'm planning to test in next week on my suite.

[magni-]

Looks like that save-always parameter doesn't actually work in practice 😞 actions/cache#1315

[kruszczynski]

Shoot, nice catch @magni-

I'll take a stab at the suggested solution from that issue.