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

[hashicorp-vault-sonar-prod]

No description provided.

[hashicorp-vault-sonar-prod]

gitar master CI is 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.
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 referenced failure.

Findings:

• The actual Build workflow (the real compile/test CI gate) on master is passing consistently across all recent runs — no test or build failures found.
• The red status is coming from a separate, manually-triggered "Releasability status" workflow run, which failed for two reasons unrelated to code in this PR:
  1. Jira: ticket SONARJAVA-7059 is still "To Do", and several others (SONARJAVA-7086, 7084, 7082, 7078, 7068, 7067, 7066, 7063, 7062, 7061, 7043) are still "In Validation" rather than "Done".
  2. QualityGate: the SonarQube quality gate for the master branch analysis is reported as failed (matches the dashboard link in the original comment, which isn't reachable from here to pull details).
• This PR's diff is empty (it's an auto-generated investigation commit), so there's no code change in this PR that could address either of these — they reflect the current state of Jira tickets and the latest SonarQube analysis, not a bug introduced by a specific commit.

This isn't something fixable via a code change in this PR. Resolving it requires moving the listed Jira tickets to "Done" and addressing whatever the SonarQube quality gate flagged on the master branch analysis directly.

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