Reduce muzzle planning overhead and support configuration caching

[sarahchen6]

What Does This Do

• Centralize muzzle planning after all projects are evaluated, sharing one Maven resolver session across modules.
• Skip version resolution and check registration for compile-only requests and modules excluded from CI aggregation.
• When runMuzzle is invoked for a specific project, include muzzle checks for its subprojects.
• Make task inputs explicit and revalidate selected dependency versions before reusing a cached task graph.

Motivation

Against master, the median configuration + graph time fell 157->101 ms (36%) for 30 modules and 116->44 ms (62%) for one selected module. Total registered checks fell 120->4 while preserving the selected module’s same 20-task graph.

These results come from Codex measuring four warm runs per variant in alternating order using offline Gradle 9.8, four workers, a shared fake dependency in a local Maven repository, a no-op scanner, and configuration caching disabled.

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	13.95 s	14.00 s	[-1.0%; +0.3%] (no difference)
startup:insecure-bank:tracing:Agent	12.81 s	12.90 s	[-1.3%; -0.1%] (maybe better)
startup:petclinic:appsec:Agent	17.14 s	16.88 s	[+0.5%; +2.6%] (maybe worse)
startup:petclinic:iast:Agent	16.92 s	16.99 s	[-1.2%; +0.3%] (no difference)
startup:petclinic:profiling:Agent	16.64 s	16.08 s	[-0.9%; +7.8%] (no difference)
startup:petclinic:sca:Agent	17.14 s	16.95 s	[+0.2%; +2.1%] (maybe worse)
startup:petclinic:tracing:Agent	16.16 s	16.10 s	[-0.5%; +1.2%] (no difference)

Commit: 84c5a27e · 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.

[sarahchen6]

Split into #12800, #12801, and #12804