Auto-infer instrumentation required helper classes at build time

[sarahchen6]

What Does This Do

Implement methodology to auto-infer instrumentations' required helper classes at build time.

Also migrate a few instrumentations from manual declarations of required helper classes to auto-detecting these classes in order to test the new methodology.

Motivation

Currently, instrumentation helper classes are manually listed for each InstrumenterModule. However, we can instead use Muzzle, which already finds class references for each instrumentation, to automatically discover which helper classes need to be loaded per instrumentation. This is similar to how OTel declares helpers.

Additional Notes

The intention is for all instrumentations to discover required helper classes at build time; however, I wanted to keep the scope of this PR low so that it's easier to review. The rest of the instrumentations will be migrated in follow-up PRs.

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.03 s	13.94 s	[-0.1%; +1.4%] (no difference)
startup:insecure-bank:tracing:Agent	12.97 s	13.02 s	[-1.0%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	17.39 s	17.26 s	[-0.3%; +1.8%] (no difference)
startup:petclinic:iast:Agent	16.70 s	17.53 s	[-8.9%; -0.6%] (maybe better)
startup:petclinic:profiling:Agent	17.49 s	17.29 s	[-0.1%; +2.3%] (no difference)
startup:petclinic:sca:Agent	17.50 s	17.48 s	[-1.1%; +1.2%] (no difference)
startup:petclinic:tracing:Agent	16.53 s	16.65 s	[-1.8%; +0.4%] (no difference)

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