Fix OpenTelemetry substitution

[geoand]

Fixes: #25143

[quarkus-bot]

/cc @radcortez

[gsmet]

Any chance we could test this somehow? Not necessarily the whole thing but at least that this thing compiles?

[geoand]

We could add the extension to one of the integration tests. @radcortez anything more we can do?

[radcortez]

We could add the extension to one of the integration tests. @radcortez anything more we can do?

We can also add some integrations tests, set up Jaeger, and check if the Telemetry data is getting correctly populated. It is going to require some effort. Not sure if it will be worth it since the plan is to move the Jaeger extension to Quarkiverse and deprecate it at some point. The recommended way to push Telemetry data is to use the OTel Exporter (which can push data to Jaeger on its own, so we don't need a dedicated extension for Jaeger).

[geoand]

So do you propose we just leave it as is for now?

[radcortez]

So do you propose we just leave it as is for now?

Yes. We can just add an integration-test to make sure that the compile works.

[geoand]

Done

[rsvoboda]

App with quarkus-opentelemetry-exporter-jaeger builds now

[geoand]

Thanks for checking!