Upgrade types.py to 2025-03-26 protocol version

[john0312]

This PR upgrades types.py to the 2025-03-26 protocol version.

Motivation and Context

This is needed to support batch JSON RPC #444

How Has This Been Tested?

All tests and type check passed.

Breaking Changes

None

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

[john0312]

The support for tool annotations #445 will probably benefit from this PR as well.

[HeetVekariya]

@john0312 PR seems good.

• We do need to add tests for this annotation functionality same as added in the Swift SDK by @mattt .
• I would like to add tests for it, as in when the PR got merged. If you are working on it, we can collaborate for the same.

[john0312]

@HeetVekariya I'm not a maintainer, so it is not my call to make on who gets to work on tool annotation tests. In fact, I'm not even certain if my PR will get reviewed/merged.

[aksheyd]

To set the optional bool default values, I think you would do:

    readOnlyHint: bool = False
    destructiveHint: bool = True
    idempotentHint: bool = False
    openWorldHint: bool = True

[john0312]

Looking through the rest of the code, the convention seems to be to set the default to None instead of False/True? I think the default convention makes sense because we want to tell if the other side specified True/False or left it absent.

Note that this PR probably conflicts with a later PR #482, in which the default is left as None as well.

Not sure if you've permission to merge, but if you do, it looks like PR #482 is likely to be merged, so maybe I'll leave the ToolAnnotations out so we can merge the rest?