SONARJAVA-6930 ci-autofix: investigate red CI

[hashicorp-vault-sonar-prod]

The latest CI run on master is red: SonarQube Code Analysis (run 102448842840).

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://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.java%3Ajava&branch=master fix it in this PR (despite it being empty for now)

[hashicorp-vault-sonar-prod]

SONARJAVA-6930

[gitar-bot]

I looked into this. The link points to the SonarQube analysis dashboard for the master branch, not to a GitHub Actions run, so there's no build/test log there to act on. This PR's own checks are currently passing/pending, not failing.

The only actual failing job on master right now is the "dogfood merge" workflow, but that's failing due to a merge conflict between the dogfood/epic-SONARJAVA-6237 branch and master (plus a broken Slack-notification step config) — an infra/branch-merge issue, not a bug in the sonar-java source that a code change here could fix.

Can you share the specific SonarQube quality gate/analysis failure (e.g. which rule or metric is failing) or a link to a failing GitHub Actions run? That will let me make a concrete fix instead of guessing.

[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