Abandon using Jaeger internal API to trace requests

[michalvavrik]

All our tests with Jaeger are using tracer URL

quarkus-test-framework/quarkus-test-service-jaeger/src/main/java/io/quarkus/test/bootstrap/JaegerService.java

Line 20 in 07b8222

public String getTraceUrl() {

to retrieve traces, that is port 16686 - HTTP JSON internal that only serve for Jaeger UI and is (theoretically) unstable. More importantly, that's not a way customers are going to retrieve traces and we are basically cheating (= my personal and highly subjective opinion). We should use gRPC/Protobuf which will be challenging in OCP scenarios.

We should implement API for traces retrieval on JaegerService so that each test don't do it on their own and we have logic that retrieves these traces at one place. Ideally, this logic uses gRPC protobuf on baremetal and maybe remain with HTTP internal till we resolve OCP issues.

Ad OCP gRPC protobuf - I think if we want to use gRPC protobuf with OCP, we will need to deal with HTTP2 routes and SSL certificates and have trusted certificate or somehow get our self-signed certificates to get trusted.