Windows Tokio Runtime Panic: "no reactor running"

[Gioee]

The SQLite MCP extension fails tests on Windows with a Tokio runtime panic: "there is no reactor running, must be called from the context of a Tokio 1.x runtime". This occurs specifically when the rmcp library performs nested tokio::spawn() calls within the async service handlers.

Root Cause: Windows IOCP (I/O Completion Ports) enforces stricter runtime context requirements than Unix platforms (Linux/macOS).

Attempted Solutions:
- Single global runtime with runtime.enter()
- Current-thread runtime to avoid worker thread issues
- Background worker thread architecture
- Explicit runtime context propagation
- Various spawn/block_on pattern modifications

Current Status: Development on this issue is paused.

Workaround: Windows tests are temporarily skipped in CI/CD workflows until a permanent solution is implemented. The extension works correctly on all Unix-based platforms.

This issue is linked with the fix-windows-tokio-issue branch.