Fix transport session id mismatch with sessionId

[CrazyHZM]

Motivation and Context

Fix #168

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

[yu199195]

good job，I also found this problem, now get the correct seesion, not inside the mcp session, but inside the transport～

[chemicL]

Thank you for the proposal! I agree we have a mismatch and we need a way to provide the session id to both the transport and the session objects. I would propose that the McpServerSession.Factory expose a new method, generateId which can be fed into both of these objects. Would you like to apply such a change?

[CrazyHZM]

Thank you for the proposal! I agree we have a mismatch and we need a way to provide the session id to both the transport and the session objects. I would propose that the McpServerSession.Factory expose a new method, generateId which can be fed into both of these objects. Would you like to apply such a change?

Yes, I'll make some revisions to this part.

[chemicL]

Thanks for the work on this. It is almost ready, a few nitpicks about imports.
As a next step we should unify the way the server transports log and include the session id everywhere. But please don't create a PR for it just yet.
@tzolov in 0.11.0 release notes we need to highlight that McpServerSession.Factory went through a breaking change impacting custom transport implementors, not end users per se.