Make sure `@sentry/cloudflare` does not conflict with `@microlabs/otel-cf-workers`

### Description

https://www.npmjs.com/package/@microlabs/otel-cf-workers

From a user

> Regarding the SDK conflicts, I had tried wrapping the Cloudflare Worker's entrypoint with the withSentry utility from @sentry/cloudflare in combination with our existing OTEL instrumentation. When applying Sentry above OTEL, Sentry would properly capture errors but we no longer received any OTEL traces from our existing instrumentation. None of our OTEL spans reached the OTEL exporter. When applying OTEL above Sentry, the Sentry SDK would introduce a Promise still pending after request completion, which the Workers runtime does not allow and will abort. Both OTEL and Sentry are wrapping the Worker entrypoint in Proxy instances to intercept the function invocations and at various points cause the other's instrumentation to behave unexpectedly.

We need to make sure that our instrumentation does not conflict with the cloudflare otel instrumentation.

Related issue: https://github.com/getsentry/sentry-javascript/issues/13365