Update README.md with comprehensive HTTP Streams transport documentation

[aatchison]

Summary

This PR updates the main README.md to comprehensively document the new HTTP Streams transport implementation and provide clear guidance on all available transport options.

Changes Made

🚀 HTTP Streams as Default Transport

• Updated all examples to show HTTP Streams as the default transport option
• Modified Docker examples to reflect the new default
• Updated code examples in the library usage section

📖 New Transport Options Section

• Added comprehensive "Transport Options" section with detailed comparison
• Documented all three transport mechanisms: HTTP Streams, SSE, and STDIO
• Included feature comparison table highlighting MCP compliance and capabilities
• Added usage examples and endpoint information for each transport

🔗 Enhanced Documentation Links

• Added links to detailed documentation for each transport type
• Created dedicated "Documentation" section with links to all guides
• Improved navigation to transport-specific documentation

✨ Key Features Highlighted

• HTTP Streams: MCP Streamable HTTP (2024-11-05) compliant, excellent proxy compatibility
• SSE Transport: Custom implementation with real-time capabilities
• STDIO Transport: Lightweight for CLI tools and scripts

Transport Comparison

Feature	HTTP Streams	SSE Transport	STDIO
MCP Compliance	✅ Full (2024-11-05)	⚠️ Custom	✅ Standard
Session Management	✅ Built-in	✅ Built-in	❌ N/A
Batch Requests	✅ Supported	❌ Not supported	✅ Supported
Web Browser Support	✅ Excellent	✅ Good	❌ N/A
Proxy Compatibility	✅ Excellent	⚠️ Limited	❌ N/A

Testing

• ✅ All 47 unit tests passing
• ✅ HTTP Streams integration tests working perfectly
• ✅ All transport mechanisms verified functional
• ✅ Documentation links verified

Documentation Updated

• Main README.md: Comprehensive transport documentation
• Links to: HTTP_STREAMS.md, SSE.md, API.md, TESTING.md

This update ensures users have clear guidance on choosing and using the appropriate transport mechanism for their use case, with HTTP Streams being the recommended default for new projects due to its full MCP specification compliance.