Undeprecate 'quarkus.otel.traces.enabled' property

[mabartos]

Describe the bug

The `quarkus.otel.traces.enabled' property is marked as deprecated, but there's no information like why it was deprecated and what's the intention. Moreover, in the docs, the property is listed there as the official way on how to disable OTel Traces.

For Keycloak, we need to also disable OTel Traces if not explicitly turned on. Deprecating or even removing the property, we will not be able to control it. I like having the unified approach for OTel Logs, Metrics and Traces as quarkus.otel.<component>.enabled.

I'd consider this issue a bug as AFAIK there's no mention of deprecating it, or suggested different approach on how to control it. It kinda seems it was done unintentionally.

@brunobat Could you please check it? Thanks!

I'll provide a PR.

Expected behavior

quarkus.otel.traces.enabled is NOT deprecated

Actual behavior

quarkus.otel.traces.enabled is deprecated

[quarkus-bot]

/cc @brunobat (opentelemetry), @radcortez (opentelemetry)

[celcius112]

@mabartos I think quarkus.otel.traces.exporter = none should do the trick. But you're right when you say that the documentation is not clear about that

[mabartos]

@mabartos I think quarkus.otel.traces.exporter = none should do the trick. But you're right when you say that the documentation is not clear about that

@celcius112 Thanks for your comment. It seems more like a hack than a supported way to disable OTel Traces. As OTel Logs, Metrics and Traces are part of the quarkus-opentelemetry extension, there needs to be a way to enable/disable them as some deployments might need only OTel Logs, without Traces, etc.