list changed handlers on client constructor

[mattzcarey]

WIP api design.

Builds off work done by @chipgpt #1068

Motivation and Context

How Has This Been Tested?

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

[pkg-pr-new]

Open in StackBlitz

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

commit: d2d0107

[KKonstantinov]

See we've extended this PR to add the same functionality for prompts and resources changes. LGTM

[KKonstantinov]

@chipgpt's PR was also correlating the server capabilities - tools.listChanged = true.

Likely we should demonstrate this here for tools, resources and prompts listChanged.

Should we also add some checks? It feels odd to allow Clients to listen for the change notifications if the server did not advertise this capability (or explicitly advertised it as listChanged: false?