Add JdbcTelemetry and JdbcTelemetryBuilder

[hannahchan]

We're currently using the JDBC library instrumentation in our application and unlike the agent instrumentation, it doesn't have an option to turn off the noisy getConnection spans. In the agent there is an option to disable jdbc-datasource and leave on jdbc.

This PR attempts to solve this by introducing an OpenTelemetryDataSourceBuilder in the library instrumentation so that consumers can through code, disable these spans.

[laurit]

@hannahchan Have a look at a few of our existing library instrumentations, for example https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/cassandra/cassandra-4.4/library/src/main/java/io/opentelemetry/instrumentation/cassandra/v4_4 Most of them follow the same style, there is a class called XxxTelemetry that have methods create, that produces an instance with default configuration, and builder that returns XxxTelemetryBuilder. The telemetry class has a method wrap (different instrumentations use different names for this method) that allows wrapping the existing instance to create a telemetry producing instance. WDYT about following the same style? As for the existing constructors in OpenTelemetryDataSource you can mark them as deprecated.

[hannahchan]

@laurit

Thanks for pointing out the examples. I've refactored my PR to what I think is following the pattern you pointed out. The only thing I'm not sure about is the name of the class I've chosen and am happy to take suggestions here. They are currently name JdbcTelemetry and JdbcTelemetryBuilder.

I'm ready for any feedback.

[hannahchan]

It looks like the build it broken and I don't know why. Is someone able to advise?

[laurit]

@hannahchan

It looks like the build it broken and I don't know why. Is someone able to advise?

We run tests agains latest version of instrumented libraries. When there is a new version sometimes our tests break, these failures don't prevent merging of the pull requests.