Remove stable/2023.1 job from master gate

stable/2023.1 is planned to be in unmaintained state[1]
and with python 3.8 drop from Tempest[2], we have to pin the
Tempest for stable/2023.1 testing[3]. This means Tempest and
its plugin master does not need to support stable/2023.1.

With that we can remove the stable/2023.1 jobs from tempest
plugin master jobs.

[1] https://lists.openstack.org/archives/list/openstack-discuss@>
[2] https://review.opendev.org/c/openstack/tempest/+/933398
[3] https://review.opendev.org/c/openstack/devstack/+/933704

Change-Id: I4721511d77c319ab4848941be8eb6d8541fe2835
diff --git a/.zuul.yaml b/.zuul.yaml
index 2a5cd41..ecda02d 100644
--- a/.zuul.yaml
+++ b/.zuul.yaml
@@ -16,12 +16,6 @@
     nodeset: openstack-single-node-jammy
     override-checkout: stable/2023.2
 
-- job:
-    name: designate-bind9-stable-2023-1
-    parent: designate-bind9
-    nodeset: openstack-single-node-focal
-    override-checkout: stable/2023.1
-
 - project:
     templates:
       - designate-devstack-jobs
@@ -34,5 +28,4 @@
         - designate-bind9-stable-2024-2
         - designate-bind9-stable-2024-1
         - designate-bind9-stable-2023-2
-        - designate-bind9-stable-2023-1
         - neutron-tempest-plugin-designate-scenario