Opentracing it

[loicmathieu]

This PR creates a Smallrye OpenTracing integration test (inspired by the OpenTelemetry one) and include a specific test for the JDBC instrumentation.

This is still a work in progress as the JDBC span is not created, but the test crash if we use the current JDBC driver version and pass if we use version 2.0.4 so it might have catch #18033 if we had it previously.

[loicmathieu]

@kenfinnigan if you can have a look at it, it's still a draft as I need to find why the JDBC span is not created.

[kenfinnigan]

Seems reasonable from a first look through

[kenfinnigan]

@loicmathieu Have you seen #18313? Are you ok with it?

[loicmathieu]

@kenfinnigan no, I'm OK to merge my changes on the new IT created for Zipkin compatibility when merged.
So let's just merge #18313 when you're OK with it, I'll rebase my changes on top of it.

[loicmathieu]

@kenfinnigan I rebase my PR onto main now that zipkin compatibility mode has been merged.
I choose to remove the existing IT that only test zipkin compatibility as my IT test way more functionality and both are not compatible (I use the mock support for easier testing).

If you think testing zipkin compatibility is important, I can copy the existing test and include it as a QuarkusUnitTest inside the deployment module of quarkus-jaeger.

[kenfinnigan]

If you could add the Zipkin compatibility test back in the deployment I think that would be good. Thanks

[loicmathieu]

@kenfinnigan

If you could add the Zipkin compatibility test back in the deployment I think that would be good.

OK, will do it

[loicmathieu]

@kenfinnigan I fix the JDBC test.

For Zipkin, there is already a test inside the jaeger extension: https://github.com/quarkusio/quarkus/blob/main/extensions/jaeger/deployment/src/test/java/io/quarkus/jaeger/test/QuarkusJaegerTracerTest.java#L29