Add comprehensive documentation and vector store factory tests

[abrookins]

• Create MkDocs documentation site with comprehensive guides
• More docs for vector store factory system with pluggable backends
• Implement unit tests for some documentation examples
• Docs for memory lifecycle management with forgetting policies
• Create Python SDK guide emphasizing client over REST API
• Add advanced vector store patterns for production usage

🤖 Generated with Claude Code

[Copilot]

Pull Request Overview

This PR adds comprehensive documentation and vector store factory tests to the Redis Agent Memory Server project. The additions include a complete MkDocs documentation site with extensive guides, unit and integration tests for the vector store factory system, and implementation of documentation-driven memory lifecycle patterns.

Key changes:

• Complete MkDocs documentation site with 15+ comprehensive guides covering all aspects of the memory server
• Vector store factory tests with pluggable backend patterns and error handling validation
• Memory lifecycle management documentation with forgetting policies and optimization strategies

Reviewed Changes

Copilot reviewed 22 out of 24 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
tests/unit/test_factory_patterns.py	Unit tests for vector store factory patterns without external dependencies
tests/integration/test_vectorstore_factory_integration.py	Integration tests for the actual vectorstore factory loading mechanism
pyproject.toml	Added MkDocs documentation dependencies
mkdocs.yml	Complete MkDocs site configuration with navigation and theme setup
docs/vector-store-backends.md	Simplified vector store backends guide emphasizing the factory pattern
docs/vector-store-advanced.md	Advanced vector store configuration patterns and migration strategies
docs/use-cases.md	Comprehensive real-world use cases across multiple industries
docs/stylesheets/extra.css	Custom CSS styling for the documentation site
docs/recency-boost.md	Detailed guide on time-aware memory ranking system
docs/quick-start.md	User-friendly quick start guide emphasizing Python SDK usage
docs/query-optimization.md	Guide on intelligent query optimization using configurable LLMs
docs/python-sdk.md	Comprehensive Python SDK documentation with tool integration
docs/memory-lifecycle.md	Memory lifecycle management with forgetting policies
docs/memory-integration-patterns.md	Three distinct patterns for integrating memory with AI applications

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The strict=False parameter in zip() is inconsistent with the length check. Since metadatas is padded to match texts length on line 226, strict=True would be more appropriate to catch any logic errors.

Suggested change

	for text, meta in zip(texts, metadatas, strict=False):
	for text, meta in zip(texts, metadatas, strict=True):

[Copilot]

This line will raise an AttributeError if the attribute doesn't exist. Use delattr(mock_module, 'nonexistent_function', None) or if hasattr(mock_module, 'nonexistent_function'): del mock_module.nonexistent_function to safely ensure the attribute doesn't exist.

Suggested change

	del mock_module.nonexistent_function # Ensure it doesn't exist
	if hasattr(mock_module, 'nonexistent_function'):
	del mock_module.nonexistent_function # Ensure it doesn't exist

[Copilot]

There appears to be extraneous function call syntax at the end of the documentation file that should be removed as it's not valid Markdown content.

Suggested change

	<function_calls>
	<invoke name="TodoWrite">
	<parameter name="todos">[{"content": "Create advanced vector store configuration examples", "status": "completed", "activeForm": "Creating advanced vector store configuration examples"}, {"content": "Add performance optimization guides for different backends", "status": "completed", "activeForm": "Adding performance optimization guides for different backends"}, {"content": "Document migration strategies between vector stores", "status": "completed", "activeForm": "Documenting migration strategies between vector stores"}]