Alexeyk/gitlab cache metadata recovery

[AlexeyKuznetsov-DD]

What Does This Do

A fix for when cache restore failed on GitHub: FATAL: unexpected EOF

Motivation

Quite a lot of jobs started to fail on GitLab randomly with error FATAL: unexpected EOF since May 22.
After some investigation I found a way to workaround the issue by clearing corrupted metadata.bin files.
That allows to restore cache as part of the build.

Additional Notes

Real issue should be fixed at GitLab. This PR is a way to unblock merging to master.

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.96 s	13.98 s	[-1.4%; +1.0%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	12.93 s	[-0.8%; +1.1%] (no difference)
startup:petclinic:appsec:Agent	16.66 s	16.30 s	[+0.7%; +3.6%] (maybe worse)
startup:petclinic:iast:Agent	16.56 s	16.67 s	[-1.8%; +0.6%] (no difference)
startup:petclinic:profiling:Agent	16.53 s	16.62 s	[-2.1%; +1.1%] (no difference)
startup:petclinic:tracing:Agent	15.74 s	16.01 s	[-2.9%; -0.5%] (maybe better)

Commit: c27a3208 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.