Refactor the USTP Workflow

[governmentSponsored]

Right now we have separate workflows in ADO for Staging and Prod and Prod is manually run.
If we combine the staging and production workflows into, one appending production onto the main workflow, we can verify a successful staging deployment and seamlessly deploy to production upon completion.

Pre-Conditions: - USTP ADO deployment workflow

• Functioning production deployment with correct data connections

Acceptance Criteria: - Production workflow triggers upon successful completion of staging workflow

• Staging failure prevents production deployment
• Can still run production deployment separately
• Ideally we would not build from the main GitHub Branch, and instead produce a build artifact after a successful staging run
• Reduce cognitive load
  -- Comb through library values and cull ones that we don't need
  -- Update documentation on library values and purposes

Pain Avoided/Frustration Saved: - No longer have to manually trigger deployments for production

• Puts checks in place to prevent an erroneous deployment of production

Breadth/Pervasiveness of Problem: - We shouldn’t have to manually deploy the production environment.

• The deployment should be a continuous workflow

Complexity of Problem (Low, Medium, High) and Why it's Complex: - Complexity is: Low-medium

• The reuse of the templates in this manner can be a bit complex