Support Progress Flow

[134130]

Motivation and Context

• There is a Progress Flow spec on MCP, but the SDK doesn't implement it.
• Related: Support progress flow #298

How Has This Been Tested?

• See: HttpServletSseServerTransportProviderIntegrationTests#testProgressNotification

Breaking Changes

• The BiFunction to construct ToolSpecification and Client constructor is changed
• Sorry for this, please let me know if there is any other way to make this feature with compatibility.

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
  • The test is not working on my MacOS device
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[brant-hwang]

This is really awesome pr! I really hope this one merged as soon as possible!

[134130]

Force-pushed with resolving conflict.

[134130]

Force-pushed with resolving conflict, again.

[tzolov]

@134130 thank you for trying to fill this missing capabilities.

But because the progress tracking introduces a breaking changes to the existing API and goes beyond the tool calling, or server side only, I've updated the #298 issue, listing the required task to implement this capability.
I submitted #351 and #352 to address the pre-requisite tasks. Once those are merged, if you are still interested you can re-work your PR on to of them.

[tzolov]

This is too generic. We would need something like progress(ProgressNotificaiton pn) instead.

[tzolov]

@134130 feel free to review #351 and #352.
I've tried to keep backward compatibility as much as possible.