Make AutoDevOps more widely applicable by adding CI_PRODUCTION_BRANCH env var
This is useful to anyone who has named their
main, or similar, and it clearly works well for projects using trunk development.
However, for projects that have a staging branch as their default branch, and who use
main, etc. for their production deployment only, the change in !53280 (merged) will mean that affected templates will stop working on their
master branch (or equivalent) and instead work on
develop (or equivalent).
A more general solution, would be to allow each project to configure both a default branch and a default "production" branch in the UI, which may be different or identical, and then make both branches available as CI variables
CI_PRODUCTION_BRANCH. That way, any project that separates out the two branches can still use the templates in the expected way.