Refactor handler context to be transport- and handler-type-aware

The current RequestContext / ServerRequestContext design has a few rough edges that warrant a dedicated refactor:

1. Request vs notification context — Request handlers have request_id and meta, notification handlers do not. Currently request_id is optional (RequestId | None) on a single shared type, which loses type safety. Ideally these would be distinct types so request handlers get a context where request_id is always present, and notification handlers get one where it does not exist.

2. Transport-specific context — The request_context field on ServerMessageMetadata is typed as Any because the server layer is transport-agnostic (e.g. it is a Starlette Request for HTTP transports, None for stdio). A better design would let transports provide their own typed context that handlers can access without casting.

These two concerns are related — both point toward making the context type more precise depending on how and where a handler is invoked.

_{AI Disclaimer}

首先沿着 handler 入口点追踪 RequestContext 和 ServerRequestContext，然后检查 ServerMessageMetadata.request_context 以及针对 Starlette Request 和 stdio 提到的传输情况。比较 request handler 和 notification handler 如何接收 context，以及如何访问特定于传输的值。在不依赖 Any 或可选 request ID 的情况下定义预期的类型边界和传输行为，即表示完成。