Moving from Jaeger exporter to OTLP exporter usage by default

[ppatierno]

This PR fixes #7592 moving from the Jaeger exporter to the OLTP exporter usage by default when using OpenTelemetry.

This PR cannot be merged yet and is in draft fot two main reason:

• it needs a new bridge 0.23.0 having OTLP as well, otherwise it will deploy KC, MM and MM2 with OTLP but old bridge 0.22.3 with Jaeger exporter
• the tracing system tests have to be updated by using Jaeger 1.35 as minimum version because it's the first version providing an OTLP endpoint.

[ppatierno]

Current status:

• for Kafka Connect and Mirror Maker system tests I already updated them to use the OTLP endpoint as collector on the Jaeger backend side
• for Bridge related test I haven't change the endpoint yet because we need a new bridge release with the OTLP exporter in (so I cannot test this PR yet)
• regarding the used Kafka clients (see KafkaTracingClients class), it seems they use the image coming from the test-clients project ... can you confirm this @im-konge ? These test clients have to be update by using the opentelemetry-exporter-otlp and we should coordinate. If we change it in the test-clients to allow this PR to work (in terms of system tests), then the regression tests could fail for other PRs still using Kafka images with old Jaeger exporter (until this one will be merged and the migration to OTLP exporter finished). Wdyt @scholzj ?

[im-konge]

@ppatierno yes, the KafkaTracingClients are using the test-clients images, but it has fixed version, so I can add PR for the opentelemetry-exporter-otlp and after that do a micro release.
After I will release it, you can use it in this PR
So we will not break anything with PR to the main branch of test-clients

[im-konge]

So, after the test-clients will be released (the micro version 0.4.1), here are all the updates needed in the code to make it work
https://gist.github.com/im-konge/1c512e5592b21e7cea533eab678ebbb7
Maybe the OTEL_TRACES_EXPORTER will not be needed, if bridge is able to have otlp as default without need of setting that env variable

[ppatierno]

@im-konge I have updated the PR using your suggestions. Could you have another pass on the PR please?

[ppatierno]

@strimzi-ci run tests test_only profile=regression testcase=OpenTelemetryST,OpenTracingST

[strimzi-ci]

❗ Systemtests Failed (no tests results are present) ❗

[im-konge]

/azp run regression

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ppatierno]

Regression includes the tracing STs and they are green, so we are good to merge. Not sure why the Jenkins one failed. Wdyt @scholzj @im-konge ?

[im-konge]

I don't think that it's related to PR, Jenkins was down or something like that in the time you triggered it

I will check it

[im-konge]

@ppatierno it failed just because we didn't have Java 17 on our containers, that should be OK now.

[ppatierno]

@im-konge thanks for checking! My point was that it's now useless running the Jenkins pipeline because you already ran the regression(s) and they include the tracing STs. Everything is green. So I can merge it.