#6583)

MCP SDK v2 changed handler signatures from (name, arguments) to
(ctx, params) and removed the request_ctx ContextVar. Add version
detection to patch the correct entry-points (Server.__init__ and
add_request_handler for v2, decorator methods for v1), extract
request context from the ServerRequestContext argument directly,
and update tests to work with both SDK versions.

Migration notes for MCP SDK v2 can be found here:
-
https://github.com/modelcontextprotocol/python-sdk/releases/tag/v2.0.0a1
-
https://github.com/modelcontextprotocol/python-sdk/blob/main/docs/migration.md

What this PR does not do:
- address all breaking changes outlined in the migration guide. This is
meant to fix the test failures on
#6567 while still being
comprehensive enough to make sense for the next developer who continues
the migration.

This was tested on the branch in
#6567 to confirm it
doesn't introduce regressions while addressing the v2 breaking change.

Fixes PY-2532
Fixes #6574

getsentry#6583)

MCP SDK v2 changed handler signatures from (name, arguments) to
(ctx, params) and removed the request_ctx ContextVar. Add version
detection to patch the correct entry-points (Server.__init__ and
add_request_handler for v2, decorator methods for v1), extract
request context from the ServerRequestContext argument directly,
and update tests to work with both SDK versions.

Migration notes for MCP SDK v2 can be found here:
-
https://github.com/modelcontextprotocol/python-sdk/releases/tag/v2.0.0a1
-
https://github.com/modelcontextprotocol/python-sdk/blob/main/docs/migration.md

What this PR does not do:
- address all breaking changes outlined in the migration guide. This is
meant to fix the test failures on
getsentry#6567 while still being
comprehensive enough to make sense for the next developer who continues
the migration.

This was tested on the branch in
getsentry#6567 to confirm it
doesn't introduce regressions while addressing the v2 breaking change.

Fixes PY-2532
Fixes getsentry#6574

Update our test matrix with new releases of integrated frameworks and
libraries.

## How it works
- Scan PyPI for all supported releases of all frameworks we have a
dedicated test suite for.
- Pick a representative sample of releases to run our test suite
against. We always test the latest and oldest supported version.
- Update
[tox.ini](https://github.com/getsentry/sentry-python/blob/master/tox.ini)
with the new releases.

## Action required
- If CI passes on this PR, it's safe to approve and merge. It means our
integrations can handle new versions of frameworks that got pulled in.
- If CI doesn't pass on this PR, this points to an incompatibility of
either our integration or our test setup with a new version of a
framework.
- Check what the failures look like and either fix them, or update the
[test
config](https://github.com/getsentry/sentry-python/blob/master/scripts/populate_tox/config.py)
and rerun
[scripts/generate-test-files.sh](https://github.com/getsentry/sentry-python/blob/master/scripts/generate-test-files.sh).
See
[scripts/populate_tox/README.md](https://github.com/getsentry/sentry-python/blob/master/scripts/populate_tox/README.md)
for what configuration options are available.

 _____________________

_🤖 This PR was automatically created using [a GitHub
action](https://github.com/getsentry/sentry-python/blob/master/.github/workflows/update-tox.yml)._

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Alexander Alderman Webb <alexander.webb@sentry.io>
Co-authored-by: Erica Pisani <hey@ericapisani.dev>