It is not clear how the transitions from gate -> candidate -> pending are supposed to happen
with a CentOS build made with the new --rhel-target option of 'none'.

With OpenJDK, we have moved to a process in RHEL where a single build
is created in a separate buildroot and then repackaged in RPMs for
each major RHEL version. However, this breaks the process of driving
everything from the CentOS side.

Our process for RHEL is:

1. Build java-<x>-openjdk-portable in java-openjdk-rhel-8-build from
the openjdk-portable-rhel-8 dist-git branch
2. Build java-<x>-openjdk RPM for RHEL 8 in java-openjdk-rhel-8-build from
the oldest z-stream branch (rhel-8.8.0 for java-

{1.8.0,11,17}-openjdk,
rhel-8.9.0 for java-21-openjdk)
3. Build java-<x>-openjdk RPM for RHEL 9 in java-openjdk-rhel-9-build from
the oldest z-stream branch (rhel-9.2.0 for java-{1.8.0,11,17}

-openjdk,
rhel-9.3.0 for java-21-openjdk)
4. Tag the two java-<x>-openjdk RPMs into each active RHEL z-stream

After a lot of work [0], we now finally have a similar process for CentOS:

1. Build java-<x>-openjdk-portable in java-openjdk-portable-build from
the openjdk-portable-centos-8 branch.
2. Build java-<x>-openjdk RPM in c8s-candidate from c8s branch
3. Bump the release number and rebuild the same java-<x>-openjdk-portable
in java-openjdk-c9s-build from the openjdk-portable-centos-8 branch
4. Tag the java-openjdk-c9s-build portable build into
java-openjdk-portable-result manually.
5. Build java-<x>-openjdk RPM in c9s-candidate from c9s branch

Once c8s is EOL, we will simplify this process and have one portable
build with java-openjdk-portable-build being based on CentOS 9 instead
of CentOS 8. At present, the above is needed to provide s390x builds
for CentOS 9 & 10, which CentOS 8 does not support.

The remaining problem we still have is that our builds in
c8s-candidate and c9s-candidate are now stuck in c8s-gate and c9s-gate
respectively (e.g. [1] [2]), and there seems to be no route for them
to transition from this.

Is there some way we can transition these and future builds into
CentOS proper? This is blocking the introduction of java-21-openjdk
into CentOS and RHEL 10, as we can not bootstrap it without
java-21-openjdk being available in the buildroot.

[0] https://issues.redhat.com/browse/CS-1618
[1] https://kojihub.stream.rdu2.redhat.com/koji/buildinfo?buildID=61135
[2] https://kojihub.stream.rdu2.redhat.com/koji/buildinfo?buildID=61191