Maybe change deployment strategy

[Greenheart]

Ideally, manually select commits that should be deployed. Especially when pushing to the main branch.

Or, we could change the main development branch to be dev and then only merge to main to create production deployments.

If we start using another development branch, we should update the CMS config to target dev instead of main.

One reason this change might be useful is because it would decrease the number of CI builds. However, we're still far below the limits, so this isn't really a problem yet.

---

Update 2023-09-25:

When merging many changes from the CMS, we can easily go beyond the rate limiting of Vercel's builds. Thus, it might be worth moving to a separate production branch that is the only one getting built by Vercel. And we can keep all existing config for main as the active development branch. Then the only changes to production should be merge commits.