Add 48h cooldown for Muzzle dependency checks

[sarahchen6]

What Does This Do

Apply 48 hr cooldown to Muzzle checks - backfill with older eligible versions when available. If the publication timestamp can't be found, warn and continue checking the version.

Motivation

We see transient failures with Muzzle checks like the ones below from just this past month that are related to Muzzle checks on partially published releases, particularly with AWS SDK artifacts that are released nearly every day. Additionally we already have a 48 hr cooldown policy for dependency upgrades for security reasons. This PR applies a similar cooldown to Muzzle checks in order to avoid these transient failures.

Example Muzzle failures on master from the past month that would've been addressed by this cooldown:

• Sep 1: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-java/-/pipelines/134488926
• Sep 3: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-java/-/pipelines/135339491
• Sep 23: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-java/-/pipelines/139379509
• Sep 25: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-java/-/pipelines/140029774

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[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	14.74 s	14.63 s	[+0.2%; +1.5%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.51 s	13.65 s	[-1.9%; -0.2%] (maybe better)
startup:petclinic:appsec:Agent	17.05 s	16.86 s	[+0.1%; +2.2%] (maybe worse)
startup:petclinic:iast:Agent	16.76 s	17.01 s	[-2.3%; -0.7%] (maybe better)
startup:petclinic:profiling:Agent	16.57 s	16.68 s	[-1.8%; +0.5%] (no difference)
startup:petclinic:sca:Agent	17.03 s	16.92 s	[-0.2%; +1.4%] (no difference)
startup:petclinic:tracing:Agent	16.08 s	16.15 s	[-1.5%; +0.7%] (no difference)

Commit: 03ed09e5 · 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.