This commit changes the restore-keys behaviour so that the order of the keys provided in the workflow is no longer respected when deciding what key to restore.

204fa1a#diff-79e9c65d7bc0c52a974cc3ca32be05e5fd06d175bfa85edbcef3af6df03ffe8dR150

This is a significant change in the behaviour and I think it's a bug.

The correct behaviour is described here: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#matching-a-cache-key

and it's clear that the cache keys should be evaluated in the order the user specified them, not after alphabetical sorting