[DPTP-4298] add supports for _cluster.yaml validation

[pruan-rht]

supports openshift/ci-tools#4646

$ ./hack/validate-prow-jobs-clusters_config.sh
2025-08-11T21:47:09+0000 Executing prow-job-dispatcher validation
{"component":"prow-job-dispatcher","file":"/Users/pruan/workspace/github_repos/dptp_team/ci-tools/cmd/prow-job-dispatcher/main.go:177","func":"main.validateConfigurations","level":"info","msg":"Validating cluster configuration...","severity":"info","time":"2025-08-11T14:47:09-07:00"}
Diff found, exit code: 1
--- /tmp/_clusters.yaml	2025-08-11 14:47:09
+++ /Users/pruan/workspace/github_repos/dptp_team/release/core-services/sanitize-prow-jobs/_clusters.yaml	2025-08-11 14:47:05
@@ -47,6 +47,7 @@
     - gpu
     - highperf
     - rce
+    disabled: true
 gcp:
   - name: build02
     capabilities:

{"component":"prow-job-dispatcher","file":"/Users/pruan/workspace/github_repos/dptp_team/ci-tools/cmd/prow-job-dispatcher/main.go:201","func":"main.validateConfigurations","level":"info","msg":"All validations passed successfully","severity":"info","time":"2025-08-11T14:47:09-07:00"}
{"component":"prow-job-dispatcher","error":"exit status 1","file":"/Users/pruan/workspace/github_repos/dptp_team/ci-tools/cmd/prow-job-dispatcher/main.go:704","func":"main.main","level":"fatal","msg":"Validation failed","severity":"fatal","time":"2025-08-11T14:47:09-07:00"}
ERROR: Changes in release/core-services/sanitize-prow-jobs/_clusters.yaml ^^^
ERROR: Running prow-job-dispatcher --validate results in changes
ERROR: To avoid breaking openshift/release for everyone you should
ERROR: fix sanitize-prow-jobs/_clusters.yaml, removing extra spaces
ERROR: comments and ordering the keys alphabetically.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pruan-rht

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [pruan-rht]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@pruan-rht: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-release-sanitize-prowjobs-cluster-config-validation	openshift/release	presubmit	Presubmit changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@pruan-rht: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ordered-prow-config	85f96fa	link	true	/test ordered-prow-config
ci/prow/generated-config	85f96fa	link	true	/test generated-config

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-bot]

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.