Deploy to master w/ new release- tag

[scottnuma]

• Previously, we created a GitHub workflow to deploy to staging when we create a release with the release prefix and then an authorized approver approves
• Let's do the same, but now for prod
• Example flow:
  • Developer merges PR and creates a new release: release-something
  • Admin approves deploying staging
  • The deploy-staging workflow runs and the change is live on staging-website.pierobotics.org
  • Developer verifies change
  • Admin approves deploying production
  • The deploy-production workflow runs and the change is live on pioneers.berkeley.edu

[render]

Your Render PR Server URL is https://website-staging-pr-639.onrender.com.

Follow its progress at https://dashboard.render.com/static/srv-c4dik54objdcsm3c3stg.

[dwai213]

For clarification, is there a particular naming convention we have to follow for the release name?
Should there be a release naming convention for developers that just want to use the deploy-staging flow to preview their code changes?

[quantumfusion]

Not sure if we should make it part of this PR, but shouldn't we change the push-staging workflow to look for a different tag? It currently appears to have the same restrictions on when to run: https://github.com/pioneers/website/blob/master/.github/workflows/push-staging.yml