Remove cinder-tox-compliance job

Until we fix our driver inheritance model, this job is almost guaranteed
to always pass. Rather than wasting gate resources for every patch, just
remove the job from the zuul pipelines for now.

It can still be run locally by calling `tox -e compliance`, so new
driver developers, and probably driver reviewers, should still run this
to make sure there is nothing missing, but that is unlikely if they
follow driver conventions.

Change-Id: I87e0de6fddad25931f71bfd7f32a218c0ed5aa98
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
(cherry picked from commit 9ce025835d)

.zuul.yaml

@@ -11,7 +11,6 @@
     check:
       jobs:
         - cinder-tempest-dsvm-lvm-lio-barbican
-        - cinder-tox-compliance
         - cinder-tox-bandit-baseline:
             voting: false
         - nova-multiattach
@@ -150,7 +149,6 @@
               - ^tox.ini$
     gate:
       jobs:
-        - cinder-tox-compliance
         - nova-multiattach
         - openstack-tox-functional-py35:
             branches: ^(?!driverfixes/).*$
@@ -374,22 +372,6 @@
       - ^releasenotes/.*$
       - ^tools/.*$
 
-- job:
-    # Test that all drivers follow the defined interface
-    name: cinder-tox-compliance
-    parent: openstack-tox
-    timeout: 2400
-    vars:
-      tox_envlist: compliance
-    required-projects:
-      - openstack/requirements
-    files:
-      - ^cinder/volume/driver.py
-      - ^cinder/volume/drivers/.*$
-      - ^cinder/interface/.*$
-      - ^cinder/backup/.*$
-      - ^cinder/zonemanager/.*$
-
 - job:
     # Security testing for known issues
     name: cinder-tox-bandit-baseline