SONARJAVA-6925 ci-autofix: investigate red CI

[hashicorp-vault-sonar-prod]

The latest CI run on master is red: Releasability check (run 102396816435).

This PR was opened with an empty commit to reserve a place for the CI fix.

[hashicorp-vault-sonar-prod]

gitar auto-apply:on

[hashicorp-vault-sonar-prod]

gitar master CI is failing https://github.com/SonarSource/sonar-java/actions/runs/34330223656/job/102396816435 fix it in this PR (despite it being empty for now)

[hashicorp-vault-sonar-prod]

SONARJAVA-6925

[gitar-bot]

gitar master CI is failing https://github.com/SonarSource/sonar-java/actions/runs/34330223656/job/102396816435 fix it in this PR (despite it being empty for now)

Looked at the failing job (https://github.com/SonarSource/sonar-java/actions/runs/34330223656/job/102396816435). This is the Releasability check workflow, and it failed for reasons outside this repo's code:

• Jira check: SONARJAVA-6868 is still "To Do"; SONARJAVA-6906, SONARJAVA-6256, SONARJAVA-6898 are still "In Validation"; SONARJAVA-6912 is still "Approved" — none are in the state required for a release.
• QualityGate check: reported as failed.

There's no source change in sonar-java that can fix this — it needs the Jira tickets moved to the correct status and the quality gate issue resolved. I'll leave this PR empty as requested since there's nothing to commit here.

[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