*This is a follow up ticket for https://issues.redhat.com/browse/AAP-7731*

We need to include this scenario in the QE pipelines.

Description

Upgrading from 2.1 to 2.3 breaks automation hub and creates an empty postgres 13 pod

Steps to Reproduce

Upgrade Operator from 2.1 to 2.3 and wait for Automation Hub to reconcile

Actual Behavior

Automation hub worker pods go into crashback loop

Migrates data to postgres 13 pod and utilizes it or don't create it at all

Expected Behavior

It comes up

Workaround

It crashes due to new mount points being configured, but the old ones aren't deleted.  Manually deleting the 2 old mount points for db encryption and settings.py or downgrading to 2.2 then upgrading to 2.3 resolves issue.

These are the lines needed to be deleted:

            - name: HUBNAME-server
              mountPath: /etc/pulp/
            - name: HUBNAME-db-fields-encryption
              readOnly: true
              mountPath: /etc/pulp/keys/