After 3.9 upgrade process, postgres migration PVC/PV is still existing after quay 3.9 upgrade completed. They are consuming customer's resource, should be removed

 quay-operator-bundle-container-v3.9.0-137

Always

1. Setup previous quay version by operator 

   - apiVersion: quay.redhat.com/v1
     kind: QuayRegistry
     metadata:
       name: registry36
       namespace: quay-enterprise-1148
     spec:
       components:
       - kind: clair
         managed: true
       - kind: postgres
         managed: true
       - kind: objectstorage
         managed: false
       - kind: redis
         managed: true
       - kind: horizontalpodautoscaler
         managed: true
       - kind: route
         managed: true
       - kind: mirror
         managed: true
       - kind: monitoring
         managed: true
       - kind: tls
         managed: true
       - kind: quay
         managed: true
       - kind: clairpostgres
         managed: true
       configBundleSecret: test-config-bundle
   

1. Upgrade to quay 3.9
2. Check pod status

postgres migration PVC/PV is still existing after quay 3.9 upgrade completed

$ oc get pvc
NAME                                  STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
registry36-clair-postgres             Bound    pvc-9379b584-a382-45a0-9732-a6b9a0c95745   50Gi       RWO            standard       66m
registry36-clair-postgres-migration   Bound    pvc-090817e0-d12a-464c-9b64-f650a414ef8d   50Gi       RWO            standard       61m
registry36-postgres-migration         Bound    pvc-60acb909-72f4-4a78-812f-be7ebccba449   50Gi       RWO            standard       61m
registry36-quay-database              Bound    pvc-77aec879-2e51-4bb7-aeb4-68aa841bd913   50Gi       RWO            standard       66m

Postgres migration PVC/PV should be removed after quay 3.9 upgrade completed