feat: use new breakability endpoint

[Jdunsby]

Description

Jira ticket: FAN-277

Updates the snyk_breakability_check MCP tool to use the Breakability API 2025-11-05 contract instead of 2024-10-15.

The generated OpenAPI client is moved to internal/apiclients/breakability/2025-11-05/, and the handler now calls CreateBreakabilityAssessments with allow_partial=true. The response shape changed from a single assessment object to an array of assessments (each keyed by package_upgrade), so a new SelectAssessment helper picks the entry matching the requested upgrade before building the tool response.

Graceful-degradation behavior is preserved: API/network failures and empty or non-matching responses still return "no additional breakability context available". Unit and handler tests are updated for the new request/response shape, including allow_partial query-param validation and upgrade-mismatch cases. Spec pull scripts and scripts/README.md are updated to reference the new API version.

Checklist

• Tests added and all succeed
• Regenerated mocks, etc. (make generate)
• Linted (make lint-fix)
• README.md updated, if user-facing
• License file updated, if new 3rd-party dependency is introduced

[CLAassistant]

All committers have signed the CLA.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[ifeanyiecheruo]

Changes look good