Dev Task: Repurpose test namespace for staging deployments

**Describe the task**
To make more effective use of our test namespace, which we previously used to basically mirror dev deployments, we can use it as a staging environment. A staging environment would be the first place to deploy the main branch to before prod, and would have representative data in the database to catch/alert us on data related issues.

**Acceptance Criteria**
- [ ] Test namespace restores data from prod backups nightly, to reflect the prod data state.
- [ ] Workflows change from a direct to prod deployment from dev, to an optional staging deployment, then prod deployment. Optional staging deployment would be considered if the change is data related or not.
- [ ] Alerts and monitoring for staging reflects that of prod, with perhaps lower thresholds

**Additional context**
- Add any other context about the task here.
- Or here

Start by reviewing the deployment workflows, test namespace configuration, production backup and restore process, and existing production alerts and monitoring. Define how nightly data restoration, optional staging promotion, and staging thresholds should work. Done means all three acceptance criteria are implemented and verified.

Written by the indexing model from the issue text.