[CHORE]: data_analysis_server — bump mcp to >=2,<3 and resolve requirements.txt conflict

[jonpspri]

Summary

After the server has been moved to this repository (tracked in #25), update mcp-servers/python/data_analysis_server/ to target MCP SDK v2 and resolve the version conflict between pyproject.toml and requirements.txt.

Changes required

1. MCP SDK version bump

# pyproject.toml — Before
mcp>=1.28.1,<2

# pyproject.toml — After
mcp>=2,<3

2. Resolve requirements.txt conflict

requirements.txt currently declares mcp>=2.0.0 while pyproject.toml declares mcp>=1.28.1,<2 — these are contradictory. After the pyproject.toml bump to >=2,<3, align requirements.txt to match:

# requirements.txt — After
mcp>=2,<3

3. API changes required by MCP SDK v2

Per the MCP SDK v2 migration guide:

• Protocol type aliases using camelCase have been removed; use snake_case equivalents.
• Review any transport constructor parameters — these may need to move to run()/app call sites.
• Validate that sync handler functions do not call asyncio.get_running_loop().

Acceptance criteria

• mcp constraint updated to >=2,<3 in pyproject.toml
• requirements.txt aligned with pyproject.toml
• All tests pass against MCP SDK v2
• CI green

References

• Depends on: [CHORE]: Move url_to_markdown_server to mcp-servers/python/url_to_markdown_server #25 (move issue)
• MCP SDK v2 migration epic: CF 1.x (x>0) - Support for MCP 2026-07-28 dual-era communication in ContextForge Gateway mcp-context-forge#6218
• Step 10 (mcp-servers update): [CHORE]: MCP SDK v2 — Update mcp-servers subpackages: FastMCP rename, dependency pins (Step 10/11) mcp-context-forge#6228