Update to auto-deploy and allow jobs to run on catalog-beta

[jbrown-xentity]

Discussed with @FuhuXia on Slack.
These changes allow us to verify various jobs and processes before cutover, and keep things on auto-deployment to remove the need for a manual push.

When we cutover, we should eventually change all these catalog-next and catalog-beta references to catalog, but that should be a simple change (and we should scan the whole repo anyways, as various services will need to change).

[FuhuXia]

• catalog-next branch is falling behind main on secririty patch and other config changes. So we will need another effort to bring catalog-next security patch up-to-date by cherry-picking from main.
• running sitemap generation on catalog-next-admin may end up with weird domain name in the sitemap files.
• cron defined in non-default branch wont get run. so we need manual trigger the tasks, or run them in cf tasks, in order to achieve the goal to verify things before cutover.

[jbrown-xentity]

Fixed the security patching if you want to re-review @FuhuXia .
True on the sitemap, although it will be accurate. We'll want to re-run that immediately after cutover.
True, cron jobs won't run. I wonder if there is a setting on that for github actions that allows other branches to run via the cron, or if that only works on the default? @neilmb can you check?