Update the OTel dependencies

[Emily-Jiang]

Update to use the latest OTel release:

1. open-telemetry/opentelemetry-java@v1.49.0...v1..60.x

The upgrade from OpenTelemetry Java v1.49 to v1.60 appears to be backward compatible from an API perspective, as evidenced by:

• No code changes required in the MicroProfile Telemetry TCK tests
• No breaking changes documented in the MicroProfile Telemetry release notes (though 2.2 notes are pending)
• All existing APIs continue to work without modification
• The changes between v1.49 and v1.60 likely include:
• Bug fixes and performance improvements
• Internal implementation enhancements
• Possible new features (additive, not breaking)
• Dependency updates
• Minor API additions (non-breaking)

2. open-telemetry/semantic-conventions-java@v1.32.0...v1.40.0

Semantic conventions updates typically include:

• New Attributes: Addition of new semantic convention attributes for various telemetry signals

• Deprecated Attributes: Marking old attributes as deprecated (especially HTTP-related ones)

• Stabilized Conventions: Moving conventions from experimental to stable status

• Updated Definitions: Refinements to attribute definitions and requirements

• New Domains: Addition of semantic conventions for new technology domains

• Requirement Level Changes: Updates to whether attributes are required, recommended, or optional

• Impact on Applications

• The semantic conventions library (opentelemetry-semconv) provides:

  • Constants for attribute keys
  • Constants for attribute values
  • Helper methods for creating attributes

• Changes between v1.32.0 and v1.40.0 would primarily affect:

  • Code using HTTP-related semantic convention constants (major changes)
  • Code using newly added or deprecated attribute constants
  • Applications needing to comply with updated semantic convention requirements

3. open-telemetry/opentelemetry-java-instrumentation@v2.15.0...v2.26.1
   Based on the code analysis, the upgrade from v2.15.0 to v2.26.1 appears to be backward compatible for the annotations API:

• No code changes required in the MicroProfile Telemetry TCK
• @WithSpan and @SpanAttribute continue to work as before
• The annotations API is stable and well-maintained

[Emily-Jiang]

Additional APIs in OpenTelemetry (Not Currently Used by MP Telemetry)
While not currently used in the MicroProfile Telemetry codebase, OpenTelemetry Java also provides:

Logs API (io.opentelemetry.api.logs) - Logging bridge (MP Telemetry 2.0+ supports this)
Events API - Semantic events
Exemplars - Link metrics to traces
Views API - Customize metric aggregation
Additional propagators - B3, Jaeger, OT Trace (available via configuration)
All these APIs are stable and backward compatible across the versions analyzed (v1.29 to v1.60 for core API, v2.15 to v2.26 for instrumentation).

[Emily-Jiang]

The configuration part of the latest OTel needs to be re-discussed to see whether MP Telemetry needs to support. @brunobat thoughts?

[Emily-Jiang]

The configuration part of the latest OTel needs to be re-discussed to see whether MP Telemetry needs to support. @brunobat thoughts?

#155 - related

[brunobat]

@Emily-Jiang I haven't used those versions because they are quite recent. Do you mind waiting a little bit while I double-check?

[Emily-Jiang]

@brunobat I would like to merge this PR. You can always provide feedback before the release.

[brunobat]

@brunobat I would like to merge this PR. You can always provide feedback before the release.

We updated to 1.59.0 and found problems we had to fix. We have no timeline for 1.60.1 yet.