CI is broken due to missing cache entries in `fail-on-cache-miss: true` steps

[obi1kenobi]

I don't recall the exact details of how CI here was set up, but I noticed that:

• We have a number of CI jobs that use a actions/cache/restore@v4 step to restore cached data.
• Those steps are configured to use fail-on-cache-miss: true, meaning the entire job fails if the cached data is not present.
• No actions/cache or actions/cache/save jobs are present to populate that cache. There is an internal cache step in the action, but it's possible we may have changed how caching happens in a way that the restore cache jobs get broken.

We need to do a bit of software archeology here, figure out how CI was supposed to run, and get it back to a working state.

Contributor help would be very welcome here, since at this point you know about as much about this CI setup as I do 😅

[memark]

You're talking about the failed CI runs for #100, right?

I don't know much about the CI setup either, but it sounds weird to fail on cache misses, I've never seen it before. A cache should be used to speed things up, not to verify certain states or conditions. I would suggest just removing that flag.

[obi1kenobi]

I think this was fixed in #103!