WIP - Autoconfigure OTel env properties with MP Config

[brunobat]

• Fixes #26444

Work:

• [x] Create data model to mimic Otel properties
• [x] PoC on MP-OpenTelemetry: https://github.com/smallrye/smallrye-opentelemetry/pull/142
• [x] Move model to quarkus and split between runtime and build time, based on the need to load classes
• [x] Refactor processors and recorders because they are too big
• [x] Using the right classloader on autoconfigure
• [x] Tweak build and runtime property scopes
• [x] translate old properties into the new system and load them if new not defined
• [x] modify producer and processor
• [x] Update setup of existing tests
• [ ] update exporter extensions
• [ ] Fix default values on ConfigMapping
• [ ] Fix issue with 2 config beans with same root
• [ ] Warn if a CDI bean is also being created as a ServiceLoader
• [ ] Deprecation of CDI beans on TracerProvider Build. Create warning on logs.
• [ ] create IT tests

[quarkus-bot[bot]]

/cc @radcortez

[brunobat]

This PR will be broken into multiple smaller PRs. We found that we don't want the configurations to be randomly split between runtime and build-time. Moreover, the extension, like it is, doesn't work properly on dev mode and we need to move the creation of the OTel SDK to runtime.

[geoand]

If we no longer want this PR, then please close it