chore: Telemetry - Make the app resilient against opentelemetry breaking changes and import failures #141
Description
This issue is inspired by recent Orchestrator startup errors related to opentelemetry import.
We should be more defensive regarding imports and dependencies. I've seen countless times that dependencies or transitive dependencies just break. Imports stop working. Attributes disappear. Functions are removed. This is even worse with uv which does not set upper bound for dependency versions. Without upper bound it's only a matter of time before imports will break. Since OpenTelemetry is a secondary feature, we need to make sure the main produce does not break when it breaks. This is especially important for OSS users, most of whom won't have telemetry enabled. The ideal solution would function even when opentelemetry or some of its modules are missing. This can be achieved by lazy imports and resilience to import errors.