Fix valid cluster UUID logic for uncommitted cluster UUIDs

[soosinha]

Description

When the condition that cluster UUID should be committed and it should be not be pointed to by any cluster UUIDs are applied simultaneously, it might skip all the cluster UUIDs. This can happen in case the last cluster UUID in a chain was uncommitted like below:

UUID1(committed) -> NA
UUID2(committed) -> UUID1(committed)
UUID3(uncommitted) -> UUID2(committed

So we need to first apply the condition of cluster UUID should be committed then reconstruct the graph and then apply the condition of clusterUUID not being pointed to by any cluster UUID.

Related Issues

#10911

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented. (Not Reqd)
  • New functionality has javadoc added (Not Reqd)
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog) (Not Reqd)
• Public documentation issue/PR created (Not Reqd)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28976/
• CommitID: e018e4f
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Compatibility status:

Checks if related components are compatible with change c6cb296

Incompatible components

Incompatible components: [https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/performance-analyzer.git]

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/sql.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/neural-search.git]

[linuxpi]

Can we add an integ test for this? maybe in a followup?

1. form a cluster and let it commit to uuid1
2. reset the cluster and let it commit to uuid2 pointing to uuid1
3. reset the cluster and let it prepublish with uuid3 pointing to uuid2, but fail publish by introducing a network partition b/w cluster manager nodes
4. reset the cluster and remove the network partition.
5. new cluster forms with uuid4 and restores from uuid2

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28986/
• CommitID: 4c046be
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/28987/
• CommitID: 4a80235
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[soosinha]

Flaky tests: #7755, #10899

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/29025/
• CommitID: 4a80235
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/29060/
• CommitID: 87a5e57
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/29065/
• CommitID: c6cb296
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[soosinha]

Flaky tests: #10006, #10755, #10154