gitlab-org/gitlab CI caching does not handle patch releases?
Noticed in https://gitlab.slack.com/archives/C101F3796/p1607396559295100
https://log.gprd.gitlab.net/goto/080547441e50f406533e6c8a73a7d717
This should probably have been an incident but it didn't page because of #619 (closed).
What appears happened here is that a patch release triggered a lot of CI, and for some reason it got cache misses on the custom CI clone cache for gitlab-org/gitlab.
