4.x Adopt MP Telemetry 1.1

[tjquinno]

Description

Resolves #8728

Major changes by component:

• Dependencies
  • MP Tel to 1.1
  • OTel to 1.29.0
  • OTel semantic conventions to 1.29.0-alpha.
• MP telemetry

  • Helidon now adds additional tags to spans (HTTP_ROUTE, NET_PEER_NAME, NET_PEER_PORT) as required by MP Telemetry 1.1.

  • Helidon now sets the span status in accordance with the OpenTelemetry semantic conventions. See https://opentelemetry.io/docs/specs/semconv/http/http-spans/#status.

  • The more recent OTel semantic conventions require the HTTP method to be in the span name for REST spans. https://opentelemetry.io/docs/specs/semconv/http/http-spans/#name This is a backward-incompatible change from MP Telemetry 1.0 and, therefore, earlier releases of Helidon 4.0.x.

    For backward compatibility with earlier releases of 4.0.x, Helidon does not by default include the HTTP method in REST span names. In this case Helidon displays a warning during start-up that the behavior is deprecated.

    Users can choose the newer, spec-compliant but backward-incompatible behavior by setting the Helidon-specific mp.telemetry.span.name-includes-method config property to true.

    The PR includes a new unit test which exercises the config setting.

  • Using

    @Inject 
    private Span span;
    

    was apparently always intended to provide access to the span that is current at the time of use, not the current span at the time of injection. This is now checked in the TCK and Helidon now conforms.

• Helidon telemetry TCK driver
  • The new TCK contains optional tests that rely on Jakarta concurrency and work only if the MP implementation under test uses that. Helidon does not so we skip those tests.
• OpenTelemetry tracing provider
  • OTel supports baggage metadata for each baggage entry. The MP Telemetry TCK now tests for that. To support that the Helidon tracing WritableBaggage API now supports a set(key, value, metadataString) method which defaults to this.set(key, value, "") The OTel tracing provider now deals with baggage metadata; the other providers ignore metadata.

Documentation

This PR adds a note to the MP telemetry page about the REST span naming incompatibility and the config option to use the newer format.