[DO NOT MERGE] ci-autofix: Investigate red master CI

[hashicorp-vault-sonar-prod]

---

Summary by Gitar

• CI Fixes:
  • Updated workflow configuration to investigate red master CI and resolve failures

_{This will update automatically on new commits.}

[hashicorp-vault-sonar-prod]

gitar master CI is failing: https://github.com/SonarSource/sonar-java/actions/runs/36445437380/job/109006425345

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR.
4. After pushing a fix, recheck the PR's CI status, and keep pushing commits until it passes.
5. If you can't fix it, leave a comment explaining your investigation.
6. If there's nothing to fix, leave a comment with your investigation notes, ending it with exactly "let's close this PR".

[gitar-bot]

Investigated the failing run: https://github.com/SonarSource/sonar-java/actions/runs/36445437380/job/109006425345

This is the "Releasability status" workflow (.github/workflows/releasability.yaml / ReleasabilityCheck.yml), which just invokes SonarSource's shared gh-action_releasability action. It doesn't build or test any code in this repository — it queries external release-readiness signals for version 8.45.0.48795:

• Jira check: ticket SONARJAVA-7059 is still "To Do", and SONARJAVA-7084, 7082, 7078, 7068, 7067, 7066, 7063, 7062, 7061 are still "In Validation".
• QualityGate check: the project's SonarQube quality gate is currently failing.

Both failures are release-state issues (Jira ticket workflow status and the live quality gate result), not a defect in any workflow file, build script, or source code in this repository. There's no code change in sonar-java that would resolve this — it requires the linked Jira tickets to be moved to Done and the quality gate issues to be resolved on the project side.

Nothing to fix here — let's close this PR.

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[hashicorp-vault-sonar-prod]

gitar master is still at 343c117e0122, but the failed run changed from 109006425345 to 109255423686, and its latest CI is still failing: https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.java%3Ajava&branch=master

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR, replacing any obsolete fix if the failure has changed.
4. After pushing a fix, recheck the PR's CI status, and keep pushing commits until it passes.
5. If you can't fix it, leave a comment explaining your investigation.
6. If there's nothing to fix, leave a comment with your investigation notes, ending it with exactly "let's close this PR".

[gitar-bot]

Investigated again.

• The referenced ID 109255423686 (from the PR's tracked state) does not resolve to any GitHub Actions job or run in this repository (404 Not Found via the API), and it doesn't appear in this repo's run history.
• The link in the comment (https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.java%3Ajava&branch=master) is not a GitHub Actions run — it's the SonarQube quality gate dashboard for the master branch.
• All of this PR's own CI checks (Build, Windows build/test, Ruling QA, Custom Rules/License Check, SonarQube Code Analysis on the PR itself, verify-sca, etc.) are passing.
• This matches the same underlying issue already identified in the previous investigation on this PR: the master branch quality gate is failing due to release-state signals (Jira tickets still "To Do"/"In Validation" and live quality-gate metrics), not because of any defect in a workflow file, build script, or source code in sonar-java. There is no code change in this repository that would fix it.

Nothing to fix here — let's close this PR.

[hashicorp-vault-sonar-prod]

gitar master has advanced from 343c117e0122 to 023d9af69637, and its latest CI is still failing: https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.java%3Ajava&branch=master

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR, replacing any obsolete fix if the failure has changed.
4. After pushing a fix, recheck the PR's CI status, and keep pushing commits until it passes.
5. If you can't fix it, leave a comment explaining your investigation.
6. If there's nothing to fix, leave a comment with your investigation notes, ending it with exactly "let's close this PR".

[gitar-bot]

Investigated again.

• master advanced from 343c117e0122 to 023d9af69637 via two routine dependency-bump merges (Update SonarSource/parent-oss monorepo to v12.0.1.87460 #6259 "Update SonarSource/parent-oss monorepo to v12.0.1.87460", Update mockito/mockito monorepo to v5.24.0 #6256 "Update mockito/mockito monorepo to v5.24.0"). Neither touches source code or build/test logic in a way that would break the quality gate.
• The linked URL (https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.java%3Ajava&branch=master) is the SonarQube quality-gate dashboard for master, not a GitHub Actions run — same as in the prior two investigations on this PR.
• All of this PR's own CI checks (Build, Windows build/test, Ruling QA, Custom Rules/License Check, SonarQube Code Analysis on the PR, verify-sca, Sanity Test, etc.) are passing.

This is the same underlying release-state issue already identified twice before on this PR: the master quality gate failure stems from Jira ticket workflow status and live quality-gate metrics, not a defect in any workflow file, build script, or source code in sonar-java. There's no code change here that would resolve it, and nothing changed in that regard with this new commit range.

Nothing to fix here — let's close this PR.

[hashicorp-vault-sonar-prod]

gitar master has advanced from 023d9af69637 to d47c44ce03b7, and its latest CI is still failing: https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.java%3Ajava&branch=master

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR, replacing any obsolete fix if the failure has changed.
4. After pushing a fix, recheck the PR's CI status, and keep pushing commits until it passes.
5. If you can't fix it, leave a comment explaining your investigation.
6. If there's nothing to fix, leave a comment with your investigation notes, ending it with exactly "let's close this PR".

[gitar-bot]

Investigated again.

• master advanced from 023d9af69637 to d47c44ce03b7 via a single merge: SONARJAVA-7043: Implemented rule S9412 "Collections.sort()" should not be used #6221 "SONARJAVA-7043: Implemented rule S9412 (Collections.sort() should not be used)". It's a normal rule addition (check + tests + ruling fixtures + doc/profile registration), nothing indicating a code defect that would break the quality gate.
• The linked URL (https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.java%3Ajava&branch=master) is again the SonarQube quality-gate dashboard for master, not a GitHub Actions run — same as in the prior three investigations on this PR.
• All of this PR's own CI checks (Build, Windows build/test, Ruling QA on all runners, Custom Rules/License Check, Sanity Test, SonarQube Code Analysis on the PR, verify-sca, Test Analyze) are passing.

This is the same underlying release-state issue already identified repeatedly on this PR: the master quality gate failure stems from Jira ticket workflow status and live quality-gate metrics on the project, not a defect in any workflow file, build script, or source code in sonar-java. There's no code change in this repository that would resolve it, and nothing changed in that regard with this new commit.

Nothing to fix here — let's close this PR.