remove hard-coded container images from docs and check tests (#165)

docs/openstack/cinder_adoption.md

@@ -446,7 +446,7 @@ configuration would go in `customServiceConfig` (or a `Secret` and then used in
 
 6. Check if any of the cinder volume drivers being used requires a custom vendor
 image. If they do, find the location of the image in the vendor's instruction
-available in the wOpenStack Cinder ecosystem
+available in the w [OpenStack Cinder ecosystem
 page](https://catalog.redhat.com/software/search?target_platforms=Red%20Hat%20OpenStack%20Platform&p=1&functionalCategories=Data%20storage)
 and add it under the specific's driver section using the `containerImage` key.
 For example, if we had a Pure Storage array and the driver was already certified

docs/openstack/glance_adoption.md

@@ -80,7 +80,6 @@ spec:
     enabled: true
     template:
       databaseInstance: openstack
-      containerImage: quay.io/podified-antelope-centos9/openstack-glance-api:current-podified
       customServiceConfig: |
         [DEFAULT]
         enabled_backends=default_backend:rbd

docs/openstack/ovn_adoption.md

@@ -67,12 +67,10 @@ spec:
     template:
       ovnDBCluster:
         ovndbcluster-nb:
-          containerImage: quay.io/podified-antelope-centos9/openstack-ovn-nb-db-server:current-podified
           dbType: NB
           storageRequest: 10G
           networkAttachment: internalapi
         ovndbcluster-sb:
-          containerImage: quay.io/podified-antelope-centos9/openstack-ovn-sb-db-server:current-podified
           dbType: SB
           storageRequest: 10G
           networkAttachment: internalapi
@@ -147,7 +145,6 @@ spec:
     enabled: true
     template:
       ovnNorthd:
-        containerImage: quay.io/podified-antelope-centos9/openstack-ovn-northd:current-podified
         networkAttachment: internalapi
 '
 ```