The Dramatiq integration is using a deprecated method to set the scope's
transaction name, use set_transaction_name instead.

"Assigning to scope.transaction directly is deprecated: use
scope.set_transaction_name() instead."

There's a test in `test_utils.py` that flakes very often, but only on
Python 3.8 and only in CI (locally it's all fine). I've tried a couple
of ways to fix it but at this point it's not worth the effort, so just
skipping it on 3.8.

The docstring for `Scope.user` says it's deprecated in favor of
`Scope.set_user()`, but there is no user-facing warning. Add one so that
we can [drop the
property](#4193) in the
next major.

---------

Co-authored-by: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com>

Remove hardcoded Litestar entries from `tox.ini`/`tox.jinja` and let
`toxgen` handle it.

(the pymongo update was pulled in by rerunning the script)

...also, `cohere` was in the `IGNORE` list twice, apparently.

We have integrations that make the python logger create breadcrumbs and
issues. This adds a third handler which creates Sentry logs on
`logger.log` statements.

Enable the logger with:
```python
sentry_sdk.init(
    ...
    _experiments={
        "enable_sentry_logs": True
    }
)

some_logger = logging.Logger("some-logger")
some_logger.info('Finished sending answer! #chunks=%s', chunks)
```

![Screenshot 2025-03-17 at 4 12
27 PM](https://github.com/user-attachments/assets/0e8dcd46-6361-47c0-8662-389fcb924969)

Refs #4150

---------

Co-authored-by: Anton Pirker <anton.pirker@sentry.io>

Fixes #2764

---------

Co-authored-by: Anton Pirker <anton.pirker@sentry.io>

Looks like strawberry is not compatible with the latest pydantic release
(2.11.0). Restrict the version of pydantic used in strawberry tests for
now.

sqlalchemy apparently released a new version which made it in by
rerunning toxgen.

The runner `ubuntu-20.04` will be removed on April 1st, 2025.

This patch makes Spotlight easier to setup by turning all sampling to
100% when no DSN is set and Spotlight is enabled. I consider this a
non-breaking and a safe change as these only apply when no DSN is set so
it should have no production or billing implications.

---------

Co-authored-by: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com>

This is breaking our test suite right now. The eco system should
stabilize in the next couple of days/weeks, then we can remove the pin.