[Docs]: Align .env template and docstrings to reflect current backend support

[hemanth678901-stack]

Documentation Type

Unclear documentation

Documentation Location

.env. template
cognee/config/context_global_variables.py(docstrings referencing backend support)

Issue Description

Following the clarification in #2103, I noticed that in some repo references (like .env template and some docstrings) still refer to only Kuzu/LanceDB as supported backends.

Given that there are now other supported backends (like neo4j_aura_dev and pgvector), it might be a good idea to update these references to reflect the current situation.
This would be a complete documentation-only patch and would not change any behavior.
Would you like me to draft a small PR for this?

Suggested Improvement

No response

Additional Context

No response

Pre-submission Checklist

• I have searched existing issues to ensure this documentation issue hasn't been reported already
• I have provided a clear description of the documentation issue
• I have specified the location of the documentation issue

[coderabbitai]

🔗 Related PRs

#179 - docs: Update README.md to include postgres [merged]
#182 - docs: Fix postgres install instruction [merged]
#235 - feat: add vector and graph dbs state to README file [merged]
#963 - Make graph authentication optional for Neo4j, Memgraph, and FalkorDB (noting enterprise-only password support) [merged]
#2015 - docs: Update .env.template [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[github-actions]

Hello @hemanth678901-stack, thank you for your interest in our work!

If this is a bug report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you.

[siillee]

Hey @hemanth678901-stack, thank you for raising this issue!

It would be great if you could draft a small PR changing the documentation on this. Check out which handlers exist in the latest code, and update the ones missing.

[muskanjoshi01]

Hi, I’m interested in working on this issue.
I have experience with Python and basic ML projects.
Can I take this up?