Adds tripleo-standalone-multinode-ipa-pipeline to templates

Currently, tripleo-standalone-multinode-ipa-pipeline is pulling
content from quay registry instead of content-provider job.
Moving this to use template which includes content-provider job
so that we pull containers from content-provider jobs.

Closes-Bug: #1960205

Change-Id: I5c0cd95a4872e9a5cdd629ba0e5dcba33a792a23
(cherry picked from commit 273019ed22)

tripleo_ipa/molecule/default/molecule.yml

@@ -6,7 +6,7 @@ log: true
 platforms:
   - name: centos8
     hostname: test-0.example.test
-    image: centos/centos:centos8
+    image: centos/centos:stream8
     registry:
       url: quay.io
     security_opts:

tripleo_ipa/molecule/deregister/molecule.yml

@@ -7,7 +7,7 @@ log: true
 platforms:
   - name: centos8
     hostname: test-0.example.test
-    image: centos/centos:centos8
+    image: centos/centos:stream8
     registry:
       url: quay.io
     security_opts:

zuul.d/base.yaml

@@ -2,7 +2,7 @@
 - job:
     description: tripleo-ipa molecule job
     name: tripleo-ipa-centos-8-molecule
-    nodeset: centos-8
+    nodeset: centos-8-stream
     parent: base
     success-url: "reports.html"
     failure-url: "reports.html"

zuul.d/layout.yaml

@@ -4,10 +4,10 @@
       - check-requirements
       - openstack-python36-jobs
       - publish-to-pypi
+      - tripleo-standalone-multinode-ipa-pipeline
     check:
       jobs:
       - tripleo-ipa-centos-8-molecule
-      - tripleo-ci-centos-8-standalone-on-multinode-ipa
     gate:
       jobs:
       - tripleo-ipa-centos-8-molecule