Fix multi-layer JDBC driver call depth calculation

[marcobjorge]

The #2756 request introduced a check on the call depth of the JDBC instrumentation that limits tracing with multi-layered drivers. For example, with Apache Calcite, the Calcite JDBC driver is caught on the call stack and none of the underlying connections are traced.

For a better support of different use cases the check should be anchored to the specific connection instead of the generic JDBC interface.

[linux-foundation-easycla]

• ❌ - Marco Jorge The commit (b3117ca) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[iNikem]

@marcobjorge please sign CLA

[marcobjorge]

@iNikem I'm on it, but I need to jump some hoops in my org first though (corporate contributor).

[laurit]

@marcobjorge just curious, would it work if you'd use -Dotel.javaagent.exclude-classes to exclude calcite classes from instrumentation when running without this change?
Perhaps an alternative would be to fix #2756 in a slightly different way. Would it work if we surrounded

opentelemetry-java-instrumentation/instrumentation/jdbc/library/src/main/java/io/opentelemetry/instrumentation/jdbc/internal/JdbcUtils.java

Line 89 in 935cb88

DatabaseMetaData metaData = connection.getMetaData();

with a thread local (or CallDepth) and only suppressed statement instrumentation when the call originates from there? Then you wouldn't need to worry whether statement.getConnection() throws exception or returns a new proxy on each call.

[marcobjorge]

@laurit I was sure it could not be done with -Dotel.javaagent.exclude-classes, but after your ask I set out to prove it and arrived at the conclusion it can and this PR is not needed (oopsy and thank you!).

TLDR: In my tests was just not excluding ALL Calcite java.sql.{Driver,Connection,Statement,PreparedStatement} in the classpath and the javaagent instrumentation was picking up something it shouldn't and therefore instrumenting the top level driver instead of the underlying drivers.