ci: improve deployment for prod & staging

[erisu]

Platforms affected

n/a

Motivation and Context

Support staging deployments & improve other CI workflows

Description

Note

Deployment to the live (production) site is no longer automatic and now requires a manual trigger.
All pushes to the main branch will automatically deploy to staging first. Once the changes are verified on staging, they can then be manually deployed to production.

• Added missing license headers to workflows
• Added staging deployment profile
• Rename current deploy.yml to deploy-prod.yml
  • Added ref to ensure it only checks out master
  • Updated actions
  • Added permissions block
  • Merged npm steps into CIT
• Added deploy-stage.yml
  • Match with deploy-prod.yml with differences for staging.

Testing

n/a

Checklist

• I've run the tests to see all new and existing tests pass
• I added automated test coverage as appropriate for this change
• Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
• If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
• I've updated the documentation if necessary

[NiklasMerz]

A staging and manual prod deploy is great. We just need to make sure we don't forget to trigger the manual deploy so there should be a note in the release docs and/or READMEs right?

[erisu]

@NiklasMerz I plan to update the docs after I merge, test, and confirm the new workflow. There are other changes coming that might require updating of the docs as well. As for deployment documentation, I will update here doc/deploying-the-website.md.