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 depends-on tempest and devstack
patches to move base jobs to Noble) and at least single job to run on
Ubuntu Jammy (for smooth upgrade from previous releases).

This commit adds a new job to run on Jammy which can be removed
in future cycle when testing runtime test next version of Ubuntu
as default.

Closes-Bug: #2088356

Depends-On: https://review.opendev.org/c/openstack/tempest/+/932156

[1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html

Change-Id: I86b6abfdbd06851f6d1b331ce113e0897384bd28

.zuul.yaml

@@ -6,6 +6,7 @@
     check:
       jobs:
         - barbican-tempest-plugin-simple-crypto
+        - barbican-tempest-plugin-simple-crypto-jammy
         - barbican-tempest-plugin-simple-crypto-secure-rbac
         - barbican-tempest-plugin-simple-crypto-2024-2
         - barbican-tempest-plugin-simple-crypto-2024-1
@@ -16,6 +17,15 @@
     gate:
       jobs:
         - barbican-tempest-plugin-simple-crypto
+        - barbican-tempest-plugin-simple-crypto-jammy
+
+# TODO(gmann): As per the 2025.1 testing runtime, we need to run at least
+# one job on jammy. This job can be removed in 2025.2 cycle.
+- job:
+    name: barbican-tempest-plugin-simple-crypto-jammy
+    description: This is integrated job testing on Ubuntu jammy(22.04)
+    parent: barbican-tempest-plugin-simple-crypto
+    nodeset: openstack-single-node-jammy
 
 - job:
     name: barbican-tempest-plugin-simple-crypto

test-requirements.txt

@@ -2,7 +2,7 @@
 # of appearance. Changing the order has an impact on the overall integration
 # process, which may cause wedges in the gate later.
 
-hacking>=3.2.0,<3.3.0 # Apache-2.0
+hacking>=7.0.0,<7.1.0 # Apache-2.0
 
 python-subunit>=1.0.0 # Apache-2.0/BSD
 oslotest>=3.2.0 # Apache-2.0