Bump OTel 1.39. and instrumentation to 2.5.0

[brunobat]

BREAKING CHANGES.

This updates the opentelemetry-java bom from 1.32 to 1.39 and the opentelemetry-instrumentation alpha bom from 1.32 to 2.50.

The breaking changes for the users are:

• HTTP semantic conventions have changed. See the full list of changes;
• quarkus.otel.semconv-stability.opt-in system property was removed because users cannot opt-in anymore;
• DB Span names have changed in the case of table creation;
• Deprecated annotation for io.opentelemetry.extension.annotations.WithSpan has been removed. Please use the new io.opentelemetry.instrumentation.annotations.WithSpan, as previously announced.

For later:

• The default OTLP protocol has been changed from grpc to http/protobuf in order to align with the specification. See Change default OpenTelemetry protocol to http/protobuf #41522

Other things to look at:

• Removed obsolete tests for the now removed @WithSpan legacy annotation.
• Removed the triple test executions depending on the value of the quarkus.otel.semconv-stability.opt-in system property. This will speed up tests considerably.
• Documentation updates.

For more details please check:
https://github.com/open-telemetry/opentelemetry-java/blob/main/CHANGELOG.md
https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/CHANGELOG.md

[brunobat]

Will squash the commits after the PR is reviewed as it makes it easy to spot change implications.

[brunobat]

This will depend on SmallRye reactive messaging changes being currently made... Will post PR here, when available.

[github-actions]

🎊 PR Preview 72af1d9 has been successfully built and deployed to https://quarkus-pr-main-41521-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[radcortez]

At least we got rid of a bunch of code :)

[trask]

❤️ sorry you have had to deal with all of the changes in these unstable components. it looks like most of the remaining unstable dependencies are related to DB, RPC and messaging semconv. I think DB and messaging semconv will be stable by end of the year, and we will start working on RPC semconv stability in the next few months. In the opentelemetry-java-instrumentation repo we are currently planning to bump from 2.x to 3.x once we are ready to switch over to stable semconv for all three (DB, RPC and messaging) by default. I noticed that you followed the opt-in flag for http which is awesome, but I would definitely understand if you didn't go through that for future updates since it's quite painful unless you are getting pushback on this from your users (in general we haven't had too much expectation of libraries emitting native instrumentation before the related semconv is stabilized).

[trask]

what do you use this module for?

[brunobat]

We need to reset for tests the GlobalEventLoggerProvider otherwise it throws an error when we execute dev mode. I remember that native would also failed without it.
It's usage comes from the SDK Autoconfiguration.

[gsmet]

@brunobat I let you squash and merge when you're ready.

[brunobat]

I think I will hold until metrics is merged.

[brunobat]

Depends on smallrye/smallrye-reactive-messaging#2677

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 59cdeca.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[ozangunalp]

Needs rebasing for version change

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit b6f5499.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/smallrye-reactive-messaging/deployment

✖ io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector - History

• Expecting actual: ["-4","-5","-6","-7","-8","-9","-10","-11"] to start with: ["-3", "-4", "-5", "-6"] - java.lang.AssertionError

java.lang.AssertionError: 

Expecting actual:
  ["-4","-5","-6","-7","-8","-9","-10","-11"]
to start with:
  ["-3", "-4", "-5", "-6"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:36)

📦 integration-tests/kotlin

✖ io.quarkus.kotlin.maven.it.KotlinRemoteDevModeIT.testThatTheApplicationIsReloadedOnKotlinChange - History

• org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase was not fulfilled within 1 minutes. - java.lang.RuntimeException

java.lang.RuntimeException: org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase was not fulfilled within 1 minutes.
	at io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase.runAndCheck(RunAndCheckWithAgentMojoTestBase.java:86)
	at io.quarkus.kotlin.maven.it.KotlinRemoteDevModeIT.testThatTheApplicationIsReloadedOnKotlinChange(KotlinRemoteDevModeIT.java:23)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)