[WIP] JMX scraper

[SylvainJuge]

This PR introduces a mew jmx-scrapper module that aims to provide replacement of jmx-metrics with the following characteristics:

• JMX MBeans and attributes mapping to metrics is defined in YAML
• YAML parsing logic is common with instrumentation and provided by the instrumenation/jmx-metrics module library.
• Groovy configuration is not supported
• Metrics are directly to an OTLP collector endpoint, there is no prometheus HTTP endpoint.

Introducing a new module allows to make future transition from jmx-metrics easier once all the currently supported target systems are included, the jmx-metrics is currently used by the opentelemetry collector through the jmxreceiver feature.

Part of #1362

This PR is a shared contribution of @robsunday and @SylvainJuge, opened as a draft to:

• provide progress status
• allow early feedback on the implementation

Scope

• support one target system: tomcat with mapping equivalent to the current tomcat.groovy.
• support for other systems will be done as separate PRs
• alignment with definitions in integration is out of scope (see JMX implementation : feature parity for target systems opentelemetry-java-instrumentation#12158 for details).

Implementation checklist

• bootstrap a new module and pick a name: jmx-scrapper
• add ability to connect to a remote JMX tree (partial copy if current impl. + unit tests), no advanced SSL support

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: SylvainJuge (07027a2, 8dfe174, f7b5a31, 71e6258, 48b095d, 586f780, 966aee6, 9072de0, d623abe, d28fd42, 5a82aac, 0f60e22, 720633c, c0ac43f, 14c0c2d, c89e527, aecf5ff, e4f4769, f8461b2, 39b6341, 1a6533e, ea46e8d, 71a5749, 378af7a, 317fcde, 91976c0)
• ✅ login: robsunday / name: Robert Niedziela (350f8a9)

[SylvainJuge]

It seems that manually squashing update commits made github actions assign lots of people, sorry for the noise here. @jack-berg can you reset this PR assignees ?

[breedx-splk]

I know this is a work in progress, but if you can find any way to try and do a series of partial PRs to keep the footprint smaller for each review that would be helpful @SylvainJuge. 😁

[SylvainJuge]

@breedx-splk I have re-framed this PR to only focus on "bootstrapping" this new module, the other implementation steps have been moved to #1362 description.

This PR is already getting quite large, so it's probably better to review and merge it before going further, I've thus marked it as ready for review.

Also, further progress is blocked unless:

• instrumentatation 2.9.0 is released Allow JMX Insight reuse for remote connections opentelemetry-java-instrumentation#12178 has been merged but missed the 2.8.0 release by a couple of commits, so we will likely have to wait for ~1 month unless a patch release is needed.
• we can use and resolve a snapshot version in the dependencies

For now, no artifact is published, so maybe having a snapshot dependency could be a temporary compromise that we could merge in main. This would help us making progress by being able to merge small chunks into main rather than an "integration branch" from a fork as we did for this PR.