Use defined project config of manila-tempest-plugin

Due to recent issues we ran into, our jobs needed to be modified
and we needed to control a few variables to be set into the stable
branches.

This change makes use of such modifications and starts using the
project config defined in the manila-tempest-plugin manifests.

Change-Id: I5ea31e1d46148045ddc92853742f2321045c5680
(cherry picked from commit 123db367ed)

zuul.d/project.yaml

@@ -6,6 +6,7 @@
       - check-requirements
       - release-notes-jobs-python3
       - periodic-stable-jobs
+      - manila-tempest-plugin-jobs-using-service-image-stable
     check:
       jobs:
         - manila-tox-genconfig
@@ -16,21 +17,12 @@
             voting: false
         - manila-tempest-plugin-dummy-no-dhss
         - manila-tempest-plugin-dummy-dhss
-        - manila-tempest-plugin-lvm
-        - manila-tempest-plugin-cephfs-native:
-            voting: false
-        - manila-tempest-plugin-cephfs-nfs:
-            voting: false
         - manila-tempest-plugin-container:
             voting: false
-        - manila-tempest-plugin-generic:
-            voting: false
         - manila-tempest-plugin-glusterfs-native:
             voting: false
         - manila-tempest-plugin-glusterfs-nfs:
             voting: false
-        - manila-tempest-plugin-zfsonlinux:
-            voting: false
         - manila-grenade:
             voting: false
         - manila-rally-no-ss:
@@ -42,7 +34,6 @@
       jobs:
         - manila-tempest-plugin-dummy-no-dhss
         - manila-tempest-plugin-dummy-dhss
-        - manila-tempest-plugin-lvm
     experimental:
       jobs:
         - tripleo-ci-centos-8-scenario004-standalone