camel-quarkus-opentelemetry2 disconnected vertx-http spans

### Bug description

I discovered this by switching the [Observability example project](https://github.com/apache/camel-quarkus-examples/tree/main/observability) from `camel-quarkus-http` to `camel-quarkus-vertx-http`.

Here's a typical view of how tracing looks. All 10 spans should be connected together, but they are split:

I think it's caused when the Vert.x HTTP Client creates its own internal spans. When tracing is suppressed on the client, then all of the Camel route spans are connected properly.

I tested with a standalone `camel-main` application and this issue does not occur when the Otel agent is used.

The workaround will be to disable internal tracing for the HTTP client. You loose a span for the request but we still have the `vertx-http` endpoint span, which contains mostly identical info.