docs: RFC for adapting Agno's knowledge/vectordb architecture into HUF

[esafwan]

Comprehensive analysis and implementation plan for bringing Agno's vector database, embedder, reader, and chunker architecture into HUF's existing knowledge system.

Key points:

• Adapt interfaces (VectorDb, Embedder, ChunkingStrategy) not the orchestration layer — keep HUF's Frappe-native pipeline
• Phase 1: Embedder system via LiteLLM (25+ providers, zero new deps)
• Phase 2: 3 vector backends (Qdrant, ChromaDB, LanceDB)
• Phase 3: Enhanced readers (Excel, PPTX) and chunkers (recursive, markdown, code-aware)
• Phase 4: Hybrid search (BM25 + vector with RRF)
• Zero breaking changes to existing SQLite FTS5 users
• All new dependencies are optional extras
• Agno is Apache 2.0 licensed — compatible with adaptation

Relationship to scoped memory/data management

This PR should be read together with #274, which proposes the bridge between conversation data management, scoped Memory/Data Records, Knowledge Sources, Agno-style retrieval architecture, and Hindsight-style long-term memory.

In that combined model, this Agno-style architecture is the indexing/retrieval half of the bridge:

Memory/Data Record selected for knowledge
        ↓
Knowledge Projection
        ↓
Agno-style indexing pipeline
        ↓
FTS/vector/hybrid retrieval

This PR should not decide what becomes canonical memory. Instead, it should improve how selected/promoted records and normal Knowledge Sources are embedded, chunked, indexed, filtered, and retrieved.

Related:

• docs: add scoped memory and knowledge bridge RFC #274 — scoped memory/data management and knowledge bridge RFC
• Add Hindsight integration evaluation and recommendation (docs) #225 — Hindsight long-term memory evaluation