Use separate cache for auto-deploy pipelines

What does this MR do?

Right now, auto-deploy tag pipelines use the shared cache. But often times, we need them to use separate cache than other builds. Because 90% of the time the stuff differing between auto-deploy pipelines are only GitLab Rails or Gitaly versions, this should be ok to do.

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

• Merge Request Title, and Description are up to date, accurate, and descriptive
• MR targeting the appropriate branch
• MR has a green pipeline on GitLab.com
• Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
• trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes
• Documentation created/updated
• Tests added
• Integration tests added to GitLab QA
• Equivalent MR/issue for the GitLab Chart opened