Implement OTEL data exporter

[radeksimko]

Context

Related: #1056

In #1327 we have added OTEL instrumentation such that we (maintainers of the LS) can have insight into the performance of various codebase parts and better understand how they each perform under stress.

We have not yet decided how and whether the tracing should be exposed to end users as there was/is a relatively long number of trade-offs to make there.

Proposal / Thoughts

• Decide how and where to send the OTEL data and how much of that should be exposed to the user
  • In generally it is agreed it should be opt in, but there's still a lot of details to iron out about what that means in practice for the UX - i.e. how exactly does the user opt in
  • Users should be informed of the nature of the data collected, regardless of how/whether they opt in - i.e. we need to have a doc page detailing this
• off-line data collection with assistance from users presents most UX and implementation challenges, but is most reasonable from privacy perspective
• Explore whether Datadog can accept delayed data ingestion - e.g. if we let users collect data into a local file and then send it to us (like a support bundle), and then we ingest it into Datadog - would DD even accept delayed data and support such a use case?