Neel Shah

Things that rely on the `scope.span` reference will only work currently with `POTelSpan` and not native otel spans. Think of the best way to wrap both of these usages.

* replace `scope.transaction` usages with `scope.root_span`

* add [resource](https://github.com/open-telemetry/opentelemetry-python/blob/c5b0244340998ad1f850997522061af7499ccf6c/opentelemetry-sdk/src/opentelemetry/sdk/trace/__init__.py#L1177) like [JS](https://github.com/getsentry/sentry-javascript/blob/4c48b07197eb4c2ff0ea141dca3a2761ec8cbdf9/packages/node/src/sdk/initOtel.ts#L109-L113) * see if using [`span_limits`](https://github.com/open-telemetry/opentelemetry-python/blob/c5b0244340998ad1f850997522061af7499ccf6c/opentelemetry-sdk/src/opentelemetry/sdk/trace/__init__.py#L1183) makes sense

Inconsistent sentry-trace and baggage values on incoming trace

3

### Version incoming trace version - 2.11.0, outgoing trace version - unknown ### Steps to Reproduce https://sentry.sentry.io/api/0/projects/sentry/sentry/events/6122ec07d3694b7ba1aa88db962afde5/json/ * `trace_id`s on the two headers are different * `sentry-trace` is sampled but...