Use stable constraint in tox to release new tag for 2024.1

We are going to release Tempest new tag to declare the start of
support for stable/2024.1. So that new tag use stable/2024.1
constraint in the tox env.

For example: if anyone use Tempest new tag in future say
1 year later then tox env also should use the 2024.1 contstraint for
compatibility instead master.

Also, making ironic-tempest-bios-ipmi-direct-tinyipa as
non voting to merge his change.

These need to be reverted once release is done.

Change-Id: I5ee1ce6b3ffbbb1f47e448fc15d540f74b21684f
diff --git a/zuul.d/project.yaml b/zuul.d/project.yaml
index 210717a..c4ad3cf 100644
--- a/zuul.d/project.yaml
+++ b/zuul.d/project.yaml
@@ -123,6 +123,9 @@
             irrelevant-files: *tempest-irrelevant-files
         - ironic-tempest-bios-ipmi-direct-tinyipa:
             irrelevant-files: *tempest-irrelevant-files
+            # TODO(gmann): make it voting again once constraints
+            # in tox.ini is changed to master.
+            voting: false
         - openstack-tox-bashate:
             irrelevant-files: *tempest-irrelevant-files-2
     gate:
@@ -154,8 +157,10 @@
         #    irrelevant-files: *tempest-irrelevant-files
         - nova-live-migration:
             irrelevant-files: *tempest-irrelevant-files
-        - ironic-tempest-bios-ipmi-direct-tinyipa:
-             irrelevant-files: *tempest-irrelevant-files
+            # TODO(gmann): make it voting again once constraints
+            # in tox.ini is changed to master.
+        #- ironic-tempest-bios-ipmi-direct-tinyipa:
+        #     irrelevant-files: *tempest-irrelevant-files
     experimental:
       jobs:
         - nova-multi-cell