Override Ceph --container-namespace for periodic jobs

If the standalone job is periodic, use 'openstack overcloud
ceph deploy --container-namespace' to pull the container
directly from quay.rdoproject.org.

Standalone scenarios usually consume containers from a
content-provider but periodic jobs pull them directly
from quay.rdoproject.org. The periodic jobs then push
them to the undercloud as a container registry. Non-
periodic jobs do not push to the undercloud registry.

When I982dedb53582fbd76391165c3ca72954c129b84a merged,
periodic standalone jobs broke because the undercloud
container registry was not configured when 'openstack
overcloud ceph deploy' was run. Because the container
prepare file has a push_destination, deployed ceph
assumes the containers were prepared in advance so it
swaps out the container namespace as indicated by
push_destination directive. Though this still happens
we override it again with --container-namespace.

Change-Id: I1abfbbd23ca93c01393d05057806ba9cc846fbed
Closes-bug: #1978998

roles/standalone/tasks/ceph-install.yml

@@ -102,6 +102,7 @@
     ssh_key: /home/zuul/.ssh/ceph-admin-id_rsa
     ssh_opt: "-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null"
 
+
 - name: Deploy Ceph via tripleo-operator-ansible
   collections:
     - tripleo.operator
@@ -127,3 +128,4 @@
     tripleo_ceph_deploy_generate_scripts: true
     tripleo_ceph_deploy_network_data: "{{ network_data }}"
     tripleo_ceph_deploy_cluster_network_name: storage
+    tripleo_ceph_deploy_container_namespace: "{{ (standalone_container_ceph_updates|bool) | ternary(docker_ceph_namespace, 'quay.rdoproject.org/tripleomastercentos9') }}"