Improve caching with sequential jobs in a workflow

[omus]

Currently a series of jobs non-matrix jobs in the same workflow would have identical cache keys with the exception of included job name. If we were to include the job name at the end of the cache key it would be possible to use a restore key without the job name allowing for the cache hits on subsequent jobs in the workflow.

I personally don't have a use case for this but we should consider this with any cache key refactoring.