Clean up OTel import structure

[sentrivana]

Problem Statement

The imports on potel-base are a bit of a mess with lots of workarounds due to circular imports. We should look into how we can restructure stuff so that it's less of a pain to work with and import.

Solution Brainstorm

Take potel-base and try to clean up how the OTel code is structured so that we have fewer imports inside functions (and less circular imports).

Some questions to consider:

• Does it make sense to have stuff stowed away in integrations.opentelemetry or should we move it higher up?
• If we go for 2 packages (tracing vs. errors-only), we should structure stuff so that it's not super complex to "turn off" OTel stuff and avoid OTel imports.