[Website]: We document OpenTelemetry SDKs/Collectors can ship data to a lot of destinations without highlighting a key difference in the data format

### Before you submit

- [x] This issue is about a documentation page, flow, or piece of content.

### Type of issue

Inaccurate

### What documentation page or section is affected

https://www.elastic.co/docs/solutions/observability/apm/opentelemetry

### What happened?

We mention OTel technologies/SDKs can be connected to mOTLP, APM Server/Integration or Elasticsearch or MIS, without really highlighting an important key aspect of the fact APM Server/Integration and MIS translate to ECS format, while the others keep an otel-native stance.

https://www.elastic.co/docs/solutions/observability/apm/opentelemetry#apm-otel-upstream:~:text=Elastic%20offers%20several%20distributions%20of%20OpenTelemetry.%20Each%20Elastic%20Distribution%20of%20OpenTelemetry%20is%20a%20customized%20version%20of%20an%20OpenTelemetry%20language%20SDK%20and%20the%20OpenTelemetry%20Collector%2C%20ready%20to%20send%20data%20to%20the%20Managed%20OTLP%20endpoint%2C%20APM%20Server%2C%20or%20directly%20to%20Elasticsearch.

https://www.elastic.co/docs/solutions/observability/apm/opentelemetry#apm-otel-upstream:~:text=You%20can%20set,managed%20intake%20service.

### Additional info

_No response_