Upgrade to OpenTelemetry SDK v 1.45 or above

[brunobat]

Description

After OpenTelemetry sdk 1.45, the OpenTelemetry protocol was moved to v1.4.0, which uses protocol buffers v4.28.3 (from v 3.25.5).
Quarkus is still on 3.x which prevents us from upgrading above.

The last OTel instrumentation that we can upgrade to, before that, is https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v2.10.0

Depends on: #44681

[quarkus-bot]

/cc @radcortez (opentelemetry)

[cescoffier]

We cannot upgrade without deeply investigating what it means for our gRPC support. My previous exploration showed a few challenges:

• the code generation was broken and needed tweaks
• the generated code was not compatible

It may have changed since, but we must be extra careful about that update.

[mapuci]

I found a pretty nasty bug in OpenTelemetry instrumentation 2.10 that causes an explosion of JVM metrics. It was fixed in June. :) open-telemetry/opentelemetry-java-instrumentation#14061

[brunobat]

I found a pretty nasty bug in OpenTelemetry instrumentation 2.10 that causes an explosion of JVM metrics. It was fixed in June. :) open-telemetry/opentelemetry-java-instrumentation#14061

Thanks @mapuci. We are upgrading directly to instrumentation 2.15, however your fix is available on Version 2.18.0, right?