Migrate to CrunchyDB in Openshift, using HELM charts

**Describe the task**
Migrate to CrunchyDB, deploying using HELM charts.

**Acceptance Criteria**
- [ ] Backup and restore process is in place.
- [ ] Migrated to using crunchy.
- [ ] Using helm charts.

**Additional context**
- We are currently using a patched version of the government patroni postgres image. We patch it with PostGIS, and then use openshift templates based on templates provided by the platform team.
- Patroni configuration, and patroni configuration within OpenShift can be complicated, and troubleshooting problems requires a fair amount of knowledge.
- There are projects that have crated HELM charts for CrunchDB deployment that include incremental backup and restore configurations.
- Switching to Crunchy will likely require server downtime. We'll probably have to shut down the database, delete PVC's, deploy Crunchy and restore.
- As of writing this ticket, we are not using HELM charts. HELM charts are great for simplifying working with openshift templates, so we'd want to migrate to using HELM.

Start by reviewing the patched Patroni PostgreSQL image and the existing OpenShift templates, then compare them with available CrunchyDB Helm charts. Done means a CrunchyDB deployment uses Helm charts and has working backup and restore processes, with migration steps accounting for the expected database downtime.

Written by the indexing model from the issue text.