Fix cache key identity for SonarJava

[guillaume-dequenne]

Part of CLP-900

Use explicit job and matrix namespaces for the Maven QA caches, and remove the synthetic POM used only to change a cache hash. Disable the overlapping cache in the shared Maven setup action. A restore-only fallback to the existing Build cache seeds each namespace on its first run; new saves remain namespaced.

Validation: PR CI passed. Both Linux ruling QA variants restored the previous Build cache through the fallback and saved distinct new keys. The custom rules job restored an exact hit for its new namespaced key. In the last 30 days, 14 of 134 commits touched a POM; the POM hash only rotates when a POM changes. A repeat run would confirm hits for the newly saved ruling keys.

[hashicorp-vault-sonar-prod]

CLP-1119

[mary-georgiou]

LGTM

[gitar-bot]

Code Review ✅ Approved

🟡 Medium risk · CI Maven dependency cache keys now use job-specific namespaces and fallback restores.

Gives Maven QA caches explicit job and matrix namespaces, removing the synthetic POM previously used to change cache hashes. A restore-only fallback to the existing Build cache seeds each namespace on first run while keeping new saves namespaced. No issues found.

Review coverage

🧪 Functional validation 1 of 1 objectives covered

📋 Rules No rules evaluated

🤖 Auto-approval Not enabled · Set up

Implementation Status ✅ 1 of 1 objectives covered

✅ CLP-900 - 1 of 1 objectives covered

This PR covers giving Maven QA caches explicit namespaces in sonar-java.

✅ 1 covered here

• ✅ Give Maven QA caches explicit namespaces in sonar-java

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Counting what did not apply, without listing it.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[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
0.0% Duplication on New Code

See analysis details on SonarQube