Update gate jobs as per the 2025.1 cycle testing runtime

As per 2025.1 testing runtime[1], we need to test on Ubuntu
Noble (which will be taken care by tempest and devstack
patches[2] to move base jobs to Noble) and at least single job to run on
Ubutnu Jammy (for smooth upgrade from previous releases).

Because of bug#2088358, we need to enabling the devstack's GLOBAL_ENV.

Tracking: https://etherpad.opendev.org/p/migrate-to-noble

Closes-Bug: #2088358
[1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html
[2] https://review.opendev.org/c/openstack/tempest/+/932156

Change-Id: I4686c922aaa639ae9dce33e1fb0fac9da78b6a93

.zuul.yaml

@@ -74,7 +74,6 @@
       tempest_plugins:
         - vitrage-tempest-plugin
       devstack_localrc:
-        GLOBAL_VENV: False
         VITRAGE_COORDINATION_URL: memcached://127.0.0.1:11211
         VITRAGE_USE_STATIC: 1
         VITRAGE_USE_DOCTOR: 1
@@ -107,6 +106,10 @@
 - job:
     name: vitrage-tempest-plugin-datasources
     parent: vitrage-tempest-plugin-base
+    # TODO(gmann): As per the 2025.1 testing runtime, we
+    # need to run at least one job on jammy. This job can
+    # be moved to Ubuntu Noble in the next cycle(2025.2)
+    nodeset: openstack-single-node-jammy
     vars:
       devstack_local_conf:
         post-config: