Fix - use enabled instead of enable-all for java 17 runtime telemetry

[cleverchuk]

Summary

Switches the Java 17 runtime telemetry configuration from enable-all to enabled, so that only additional JFR-sourced metrics are collected instead of duplicating metrics already available via JMX.

Details

The SolarwindsPropertiesSupplier class supplies default OpenTelemetry configuration properties when the agent is enabled. One of these properties controls the Java 17 runtime telemetry instrumentation.

The previous property key otel.instrumentation.runtime-telemetry-java17.enable-all activates all JFR-based runtime metrics, including those that overlap with metrics already collected through JMX. This results in redundant data collection for metrics that JMX already provides.

The new property key otel.instrumentation.runtime-telemetry-java17.enabled activates only the supplemental JFR metrics that are not available via JMX, avoiding the duplication.

One trade-off is that jvm.system.cpu.utilization will no longer be available, as it is only exposed through the enable-all configuration. However, reverting to enable-all just for that metric would re-introduce the full set of duplicate JMX metrics, which is not what we want. Hence, we should remove it from the dashboard.

Test services data

1. e-1712644058766987264
2. e-1712643928659124224
3. e-1742334541200846848
4. e-1777406072376840192

[tammy-baylis-swi]

Sounds good