Align EDOT docs wording for Managed OTLP targets and crash reporting support

[Copilot]

This addresses the repo-local coherence findings in the docs sweep by removing wording that implied EDOT Cloud Forwarder targets only Serverless and by tightening the crash reporting description to match the EDOT SDK support matrix.

• Managed OTLP target wording

  • Updated the EDOT Cloud Forwarder overview to describe the Managed OTLP endpoint as an Elastic Cloud target, which matches both the page’s applies_to metadata and the mOTLP reference docs.

• Crash reporting support wording

  • Narrowed the EDOT-vs-upstream comparison table entry from generic “mobile platforms” wording to supported platforms, explicitly noting current iOS-only support.

• Scope

  • The APM Server destination contradiction called out in the sweep points to a page in the separate docs-content repo; this PR only resolves the findings that are editable in elastic/opentelemetry.

-{{edot-cf}} sends the data it collects directly to the ... endpoint of {{serverless-full}}.
+{{edot-cf}} sends the data it collects directly to the ... endpoint of {{ecloud}}.

-| Crash reporting | Available in EDOT only. Captures native crash data on mobile platforms for post-mortem analysis. |
+| Crash reporting | Available in EDOT only. Captures native crash data on supported mobile platforms (currently iOS only) for post-mortem analysis. |