chore!: Remove Jaeger support

[sbernauer]

Description

https://crates.io/crates/opentelemetry-jaeger stopped pushing new versions, so we can either:

1. Rip out Jaeger support (in favor of otlp)
2. Don't update the whole opentelemetry ecosystem

As the removal of Jaeger was planned in any case and I'm not aware of any Jaeger usage (in operator-rs, not talking about webhook and co.), I would prefer the first.

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

# Author
- [ ] Changes are OpenShift compatible
- [ ] CRD changes approved
- [ ] Integration tests passed (for non trivial changes)

# Reviewer
- [ ] Code contains useful comments
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)

# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added

[NickLarsenNZ]

LGTM

I just had to see what the .tracer(...) was doing, but I see they switched from returning a Result<Tracer, _> to a Result<TracerProvider, _>, hence the addition to get the Tracer.

[nightkr]

Wait.. so we don't support any opentelemetry target at all now then? Is there anything blocking OTLP support? Was there a pressing need for this upgrade? Doesn't removing the exporter support remove what impetus there was for upgrading the dependency?

Also please try to actually describe the change in the PR title. Removing a feature is not a "dependency bump".

[sbernauer]

Honestly I don't have answers to those questions, what do you think of reverting the opentelemetry bump?
Yes, the PR title is bad, it spiraled out, sorry!

[nightkr]

Yeah I would hold it back for now and make an issue about migrating.

[sbernauer]

Makes sense, please have a look at #832

[NickLarsenNZ]

For future reference, I would have liked to be involved in this conversation (and the decision to do #832). Somehow I missed any notifications for it.

IMO, we should remove opentelemetry-jaeger, as it is deprecated. It doesn't mean Jaeger can't be used, but tracing should be transported via OTLP (which Jaeger supports).

I propose we:

1. Deprecate this initialize_logging function (see 2).
2. Upgrade operators to use the new stackable-telemetry initialisation (which replaces the functionality in 1).
3. With the removal of the logging function, opentelemetry-jaeger will be gone and will not hold us back from future opentelemetry version bumps.

---

Edit: By involved, I meant on the revert of this PR. Somehow I missed the @ mention, so that's on me. I'm happy to receive slack messages.

[Techassi]

I agree with @NickLarsenNZ's comment and would have also liked to be involved since he and I worked on the stackable-telemetry crate which is the next step towards better telemetry via OpenTelemetry (and OLTP).

This change is especially weird, because it was done during simple dependency bumps.

[NickLarsenNZ]

This change is especially weird, because it was done during simple dependency bumps.

Just for clarity, the dependency bump is not compatible with jaeger anymore, hence it being dropped.

[sbernauer]

@NickLarsenNZ and I talked about this and are happy to talk to you @Techassi when you are back :)