JBAI-19233 Split tracing of the LLM clients' OkHttp handlers

[Vladislav0Art]

Description

1. Moved okhttp-related components (i.e., okhttp instrument, OpenTelemetryOkHttpInterceptor, patchOpenAICompatibleClient, utility patchInterceptors) into a newly created module tracing:okhttp (split these components into several files).
2. Moved Ktor-/okhttp-related extension functions into tracing:ktor and tracing:okhttp modules, respectively.
3. Updated imports and deps of the LLM providers.

Closes: JBAI-19233 Split tracing of the LLM clients' OkHttp handlers, similar to how Ktor is implemented?

Important Notes

Right now, tracing:core still has dependencies on both Ktor and OkHttp libraries! It's so because we use ktor.http.ContentType, some other Ktor and OkHttp components throughout the entire modules (e..g, LangfuseExporterConfig uses Ktor's HTTP module). I tried to remove both dependencies completely, but it requires a lot of effort (e.g., we need to implement custom ContentType, MediaType, HttpHeaders, and more).

If we plan to eradicate HTTP-specific dependencies from the tracing:core, it should be done step-by-step and into several PRs.

This PR only splits okhttp tracing-related functionalities into a separate module; nothing more.

[Vladislav0Art]

State: postponed for now in favor of major refactoring (PR) and further removal of dependencies on the Ktor module (PRs are tbd).