fix: add UnsupportedCapabilityError to handle capabilities custom exception

[matteo-gobbo]

Replace generic Error with UnsupportedCapabilityError when capabilities are not supported, allowing applications to distinguish capability errors from actual failures.

Motivation and Context

It fixes the issue #430

How Has This Been Tested?

Breaking Changes

There are no breaking changes.

Types of changes

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

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

Added UnsupportedCapabilityError class in packages/core/src/types/types.ts.
I assigned to it an error code of -32043 following what's been done before, but it should be checked if it's correct.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 78bb55b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/client@1329 

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/server@1329 

commit: 78bb55b