Create Issues from OpenTelemetry exceptions (OTLP exception log records and span events)

Problem Statement Applications instrumented only with OpenTelemetry can send traces and logs to Sentry's OTLP endpoints, but their exceptions never become Issues: • Exception span events (the current default way OTel SDKs record exceptions, via span.recordException) are dropped on OTLP ingest. Sentry's docs say "All span events are dropped during ingestion". • Exception log records (where OTel is moving exceptions: OTEP 4430, OTEL_SEMCONV_EXCEPTION_SIGNAL_OPT_IN=logs) are stored as logs only. So OTel-only services get no Issues, alerts, grouping, suspect commits or Seer for their errors, even though the data contains everything an error event needs: exception.type, exception.message, exception.stacktrace (semconv), plus trace and span ids. Solution Brainstorm Build on the generic log → Issue capability in #113802, with an exception-aware path for OTel: 1. Exception log records → error Issues. Records with event_name exception / *.exception, or wit…