OpenTelemetry SDK Autoconfigure

[radcortez]

Description

Provide support for OpenTelemetry SDK Autoconfigure:
https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md

Scheduled work:

We identified improvements (see comments bellow) to the initial PR #26760
Leading to this phased execution plan:

• Refactor classes to align with metrics binding packages. This will reduce complexity from current processors.
  Refactor OpenTelemetry extension #28314
• Move opentelemetry-exporter-jaeger to quarkiverse.
  Move opentelemetry-exporter-jaeger from Quarkus to Quarkiverse quarkiverse/quarkus-opentelemetry-exporter#1
• Move opentelemetry-exporter-otlp to otel project because it doesn't make sense not to have a default exporter .
  Move opentelemetry-exporter-otlp to opentelemetry. Remove opentelemetry-exporter-jaeger #28487
  Drop quarkus-opentelemetry-exporter-jaeger from main quarkus-platform#647
  Drop quarkus-opentelemetry-exporter-jaeger from 2.13 branch quarkus-platform#648
  Merge quarkus-opentelemetry-exporter-otlp into quarkus-opentelemetry  quarkus-super-heroes#161
  Merge quarkus-opentelemetry-exporter-otlp into quarkus-opentelemetry quarkus-quickstarts#1191
  Wiki release notes (TBD)
  Update links for published docs on the quarkiverse extension (TBD)
• Move OTel SDK to runtime and fix dev mode reload.
  Fix vertx otel sdk reload in devmode #28792
• Replace with new configs and new autoconfigutation from OTel + documentation.
  OpenTelemetry extension re-write using the SDK AutoConfigure #30033

Required by:

• OpenTelemetry: Custom sampler config; rate-limiting sampler #26438
• Provide OpenTelemetry OTLP/HTTP exporter #21535
• Support exclusion of non-application URIs if custom Sampler is used #26367

[brunobat]

The idea is to mirror the OTel side configs in order to better document the features on our side. This will require some work on our side but will improve the dev experience because there will no ambiguity on the working configs and which OTel config version is being supported.

[brunobat]

The existing WIP PR tried to allign as best as possible the current OTel extension and the OTel side autoconfiguration. However, the PR #26760 will be closed and incremental PRs will be done because:

• PR is already too big and difficult to review
• We learned that the resulting configuration objects are confusing. There is no clear separation from build and runtime configs.
• This doesn't solve the current dev mode auto-reload problem, which will require build and configuration changes. Most pieces of the PR will be moved to PRs with the plan detailed in the 1st comment.

[brunobat]

Finally done