[Server] SEP-2663 Tasks: TaskStoreInterface with InMemory and PSR-16 stores

Task persistence for SEP-2663 for the 2026-07-28 release. Tracked by umbrella #335.

Scope

• Mcp\Server\Task\TaskStoreInterface: save(), get() (null for unknown or expired — a client cannot tell them apart and does not need to), delete().
• InMemoryTaskStore with a task limit (default 1000, oldest-by-last-use evicted) so unbounded task creation cannot exhaust memory. Right for stdio and single-process runtimes; wrong under PHP-FPM, where the worker that creates a task is not the one polled for it.
• Psr16TaskStore (PSR-16 cache-backed) for PHP-FPM — a filesystem adapter covers the "file store" case, so no separate FileTaskStore.
• Expiry is TTL-based (Task::isReadable() on read, cache TTL for PSR-16) plus the in-memory limit; no request-counted GC pass.
• The store is the one place both server-side task state and the pending server→client asks (Task::$inputRequests) live.
• The store is handed to TasksExtension, not to the builder (see #346).

Commencez par localiser TasksExtension, Task::isReadable() et les points d’entrée proposés de TaskStoreInterface. Suivez la manière dont l’état des tâches côté serveur et Task::$inputRequests sont transmis à l’extension, puis définissez les responsabilités de InMemoryTaskStore et Psr16TaskStore. Le travail est terminé lorsque save/get/delete fonctionnent avec expiration, qu’une éviction bornée du plus ancien selon la dernière utilisation existe en mémoire et que le comportement TTL de PSR-16 prend en charge PHP-FPM.