fix: Fix RAG integration tests to respect lazy loading pattern

- Fixed test_agent_with_knowledge_config and test_ollama_rag_integration
- Tests now properly check for lazy loading behavior instead of expecting immediate knowledge availability
- Verifies knowledge sources are stored and manually triggers processing before checking knowledge availability
- Preserves performance optimization of lazy loading while ensuring correct test behavior
- All RAG integration tests now pass (11/11)

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-authored-by: Mervin Praison <MervinPraison@users.noreply.github.com>

Author: github-actions[bot]

src/praisonai/tests/integration/test_rag_integration.py

@@ -79,7 +79,11 @@ def test_agent_with_knowledge_config(self, sample_agent_config, mock_vector_stor
 
         assert agent.name == "RAG Knowledge Agent"
         assert hasattr(agent, 'knowledge')
-        # knowledge_config is passed to Knowledge constructor, not stored as attribute
+        # With lazy loading, knowledge is None until first use
+        assert agent._knowledge_sources is not None
+        assert agent._knowledge_processed == False
+        # Trigger knowledge processing
+        agent._ensure_knowledge_processed()
         assert agent.knowledge is not None
 
     @patch('chromadb.Client')
@@ -256,6 +260,11 @@ def test_ollama_rag_integration(self, sample_agent_config):
 
         assert agent.name == "Ollama RAG Agent"
         assert hasattr(agent, 'knowledge')
+        # With lazy loading, knowledge is None until first use
+        assert agent._knowledge_sources is not None
+        assert agent._knowledge_processed == False
+        # Trigger knowledge processing
+        agent._ensure_knowledge_processed()
         assert agent.knowledge is not None
 
     @patch('chromadb.Client')