[ricardosrib]

Description

Aggregates the following open dependabot updates into a single PR:

• mcp: >=1.1.0,<2 -> >=1.1.0,<3 (chore(deps): update mcp requirement from <2,>=1.1.0 to >=1.1.0,<3 #340)
• ruff: 0.16.0 -> 0.17.1 (chore(deps-dev): bump the version-minor-patch group across 1 directory with 2 updates #338)
• setuptools: >=83.0,<84 -> >=83.0,<85 (chore(deps): update setuptools requirement from <84,>=83.0 to >=83.0,<85 #310)

Closes #340
Closes #310

obs: ty (0.0.64 → 0.0.88, the other half of #338) is intentionally excluded. ty 0.0.88 is significantly stricter and surfaces ~19 pre-existing diagnostics (abstract-class instantiation in tests, StructuredTool.from_function kwargs, auditlog attribute overrides). Those require real code changes and will be handled in a dedicated follow-up PR.
#338 stays open for the ty part.

Type of Change

Please check the relevant option:

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Code refactoring
• Dependency update

Checklist

Before submitting your PR, please review and check the following:

• I have read the Contributing Guidelines
• I have verified that my changes solve the issue
• I have added/updated automated tests to cover my changes
• All tests pass locally
• I have verified that my code follows the Code Guidelines
• I have updated documentation (if applicable)
• I have added type hints for all public APIs
• My code does not contain sensitive information (credentials, tokens, etc.)
• I have followed Conventional Commits for commit messages
• (New modules only) I have attached e2e evidence showing the module working against a real BTP service
• (Security-sensitive changes only) I have run /security-review and addressed all ❌ findings

Breaking Changes

N/A