McpServerSession lifecycle doesn't support distributed services

This issue is closely related to #273 and could be considered as a follow up to that, but I decided to split it for convenience and readability.

Consider an MCP server written with this SDK and using the StreamableHttp transport. We deploy two replicas (A and B) of this server, with a load balancer in front.

1. A new client application initiates a session by sending an initialize message, followed by a notifications/initialized notifications.
2. Let's say that the Load Balancer routed both messages to replica A
3. As a result, replica A generated a new session which Id is communicated back to the client
4. Replica A now has an McpServerSession instance properly initialized with all the necessary client information

Problem:

1. Next the client sends a tools/list message with the obtain sessionId, but this time the load balancer routes the message to replica B
2. Even though I believe it should be the server's responsibility to share the session id across replicas, the McpServerSession instance that lives in replica B has never received (and will never receive) the initialize message and notifications
3. Although it's possible to distribute all that state and simulate that handshake in replica B (I actually did it), I think this SDK should have an OOTB support for that, or at the very least, SessionFactory methods that make it easier to generate "ready to use" Sessions based on previous initializations.

Commencez par lire cette issue avec l’issue associée #273, puis suivez le cycle de vie de la session StreamableHttp, de initialize et notifications/initialized jusqu’à tools/list. Inspectez les points d’entrée de la gestion des sessions et de SessionFactory mentionnés dans l’issue. Le travail est terminé lorsqu’une session initialisée sur la replica A peut être utilisée sur la replica B sans simuler manuellement le handshake.