feat: CE-625 Round 2

[barrfalk]

Description

The goal of this PR is to ensure that there’s always an ever-present deployment of Case Management in the dev environment that matches what’s in test. Deployments to dev/test (and eventually prod) are handled via helm and argo. When a PR is approved and moved to test, an image is uploaded to GHCR (github container repo) with a specific tag (a sequential number). The github action for test deployments has been updated to set the tag in values-static.yaml. Argo detects changes to this file and deploys it if there are any changes. Since this file is updated with the same tag used for test deployments, argo should deploy the same test image to the dev environment (argo itself knows that values-static.yaml is associated with the dev environment, that information isn’t within the ghcr image).

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Unable to test until migrated to test.

Checklist

• [x] I have read the CONTRIBUTING doc
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have already been accepted and merged

Further comments

---

Thanks for the PR!

Deployments, as required, will be available below:

• Backend

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow