…3813)

This reverts commit 84187ea.

…potel-base

It is not ready yet and i do not want to push dog fooding back again.

extracted from
https://github.com/getsentry/sentry-python/pull/4487/files with lots of
manual fixes

* migrate old style `# type: bla` to inline types
* most importantly use
[`__future__.annotations`](https://peps.python.org/pep-0563/#enabling-the-future-behavior-in-python-3-7)
so that we can simply use forward annotations without wrapping them in
strings like we did before, this simplifies things substantially
* also guard only things that shouldn't be imported under
`TYPE_CHECKING`, in the future it seems we should avoid using
`TYPE_CHECKING` completely
* #4510
* #4522
* #4529
* #4530
* #4532
* #4533
* #4534

closes #2585

Ensure tag values are strings before serializing an event or a
transaction to an `Event` dictionary.

Fixes #4391

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Ivana Kellyer <ivana.kellyer@sentry.io>

We currently use an `if self._ctx_token` check to determine if a span
has a `_ctx_token`. However, this check is incorrect, since `_ctx_token`
is only sometimes set. Furthermore, when `_ctx_token` is set, we should
always have a `_ctx_token`.

Therefore, using `hasattr` is what we want.

<!-- Describe your PR here -->

---

Thank you for contributing to `sentry-python`! Please add tests to
validate your changes, and lint your code using `tox -e linters`.

Running the test suite on your PR might require maintainer approval.

Closes #3149

…potel-base

Port the `openai-agents` integration to `potel-base`.

---------

Co-authored-by: Ivana Kellyer <ivana.kellyer@sentry.io>
Co-authored-by: Anton Pirker <anton.pirker@sentry.io>

The main change is that `op` is now optional and `name` and
`description` are basically interchangeable and map to each other as
best as possible.

Preference is given to explicitly set values (`SentrySpanAttribute`) and
if not (in the case of pure otel spans), we try to derive them. The
entire flow is **much** cleaner now instead of repeated calls to the
same attributes.

(For the main mapping changes in `opentelemetry/test_utils` I'd
recommend reading the new code instead of the diff.)

Allow to turn off span creation based on span origin.

This is a nice-to-have that's useful when you're double instrumenting a
library with e.g. Sentry and OpenTelemetry and you want to turn off
Sentry spans. (On the OTel side you can also disable specific
instrumentation. By adding the possibility to do this on the Sentry side
of things, we enable users to pick whichever they prefer.)

All our integrations follow the `setup_once` logic while the otel
patching was being done for each `Client` again leading to recursive
patching.
This was revealed by removing the transport test forks.