Remove scenario 03/04 tests from CI

We should have removed these when we removed the tox targets[1].

[1] 6e7a5725fa90e66c060a06a8ffe5e5454fd7a7b6

Change-Id: I4bdf987ea52479ef7790fc506158a57d8d060dc5

.zuul.yaml

@@ -12,20 +12,6 @@
       tox_envlist: py310-func-scenario02
       bindep_profile: rabbit kafka amqp1
 
-- job:
-    name: oslo.messaging-tox-py310-func-scenario03
-    parent: openstack-tox-py310
-    vars:
-      tox_envlist: py310-func-scenario03
-      bindep_profile: rabbit amqp1
-
-- job:
-    name: oslo.messaging-tox-py310-func-scenario04
-    parent: openstack-tox-py310
-    vars:
-      tox_envlist: py310-func-scenario04
-      bindep_profile: kafka amqp1
-
 # Begin v3 native jobs
 # See https://docs.openstack.org/devstack/latest/
 
@@ -112,10 +98,6 @@
         - oslo.messaging-tox-py310-func-scenario01
         - oslo.messaging-tox-py310-func-scenario02:
             voting: false
-        - oslo.messaging-tox-py310-func-scenario03:
-            voting: false
-        - oslo.messaging-tox-py310-func-scenario04:
-            voting: false
         - oslo.messaging-src-dsvm-full-rabbit
         - oslo.messaging-src-dsvm-full-amqp1-hybrid:
             voting: false