Regular update

Adds supports for variants, i.e., the same test suite running with a
slightly different setup (for instance, a different set of dependencies,
like `openai` and `openai_notiktoken`).

To add a variant, simply add a new test suite to the config.

The tricky part is naming. I had to rename `openai` to `openai_base`
since otherwise the `openai_notiktoken` and `openai_agents` test suite
would be run with `tox -e py<version>-openai` / `./scripts/runtox.sh
py<version>-openai` due to how tox works. They should be treated as
three different suites.

Closes #4507

- move the langchain test suites to be governed by toxgen
- this indirectly results in removing the `-latest` tests in the AI
group 🎉
- `-latest` tests predate toxgen and langchain was the last non-toxgen
test suite (the rest was just skipped) -- all AI tests are now pinned
- updated the naming scheme to use dashes instead of underscores for
variants so that it's clearer if something is part of the name of the
integration or if it denotes a variant
- for instance, `openai-base` means this is the `base` variant of the
`openai` test suite, but `openai_agents` means this is the
`openai_agents` test suite (no variant)

I'm explicitly ignoring the two alpha versions of 1.0 since adapting the
integration to work with those is out of scope: [dedicated
issue](#4735)
  
Part of #4506

Add parameter to the method capturing exceptions in the OpenAI integration, to determine if the span context is closed with __exit__() or not. The option is used to prevent double exit scenarios when a span context is managed automatically.

Related to: #4723

)

Set Pytest command-line argument to return non-zero exit code when an unraisable exception is encountered.

Closes #4723.

Forgot to remove these two from the toxgen ignore list. Shouldn't have
any actual effect on tests since the test suites are now called
differently.

A new version of `openai`, which is a dependency of `openai_agents`,
[came out an hour ago](https://pypi.org/project/openai/#history), which
[broke](https://github.com/getsentry/sentry-python/actions/runs/17405958869/job/49410259073)
our CI. Pinning for now.

I followed how other functions in the SDK are typed. For example, other
wrappers have the signature `(F) -> F` for a type variable `F`, although
here the function can be async as well.

Closes #4663

…4719)

Ref #4718

Does not solve the underlying issue and might leave things in an
inconsistent state, but it's still preferable to letting an error bubble
up to the user.

This is not a fix -- it just makes the SDK not propagate an internal SDK exception upwards.

Adds an uncaught exception integration, enabled by default. The
integration forwards the exception to Sentry only if the exception value
and stacktrace are set.

Closes #374

- actually support dashes in integration names in `tox.ini`/toxgen
- make `split_tox_gh_actions.py` actually fail if it fails to parse
`tox.ini`

Context: `split_tox_gh_actions.py` was actually failing because it
assumed there can't be dashes in test suite names, but since it was just
printing the error instead of actually exiting with an error code, we
didn't notice this in CI.

Remove hardcoded arq config, generate with toxgen instead.