feat: crunchy deployment

[jon-funk]

• Infra to deploy shared crunchy cluster per namespace
• per PR database+user created and cleaned up on PR close
• adds a useCrunchy flag so that devs can disable/enable crunchy for their release, which is on by default in dev

In the future, after data migration we will set this as the default and retire the bitnami pg instance

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• deploymnt of crunchy,
• user cleanup
• PR close works
• use crunchy flag works

Checklist

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Further comments

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

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

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

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

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[jon-funk]

testing close

[sonarqubecloud]

Quality Gate passed

Issues
18 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mikevespi]

Awesome stuff! 🚢

[afwilcox]

All Openshift objects should follow naming convention: nr-compliance-enforcement-{pr number | test | prod}-*