Create EloqKV FAQ hub for SEO/GEO answer capture

[liunyl]

Epic: #47

Background

A single strong FAQ hub is preferable to many thin FAQ pages. It should answer high-value questions in a format that search engines and AI systems can quote accurately.

Tasks

• Create /faq/eloqkv or equivalent FAQ hub.
• Include short direct answers plus detailed explanations for core questions:
  • What is EloqKV?
  • Is EloqKV a Redis replacement?
  • How does EloqKV reduce Redis cost?
  • Can EloqKV persist data?
  • How is EloqKV different from Redis AOF always?
  • Does EloqKV support Redis and Valkey clients?
  • When should I still use Redis?
  • What workloads are best for EloqKV?
• Link answers to relevant product, docs, benchmark, and article pages.
• Add FAQPage schema aligned with visible content.

Acceptance criteria

• Each answer starts with a 1-2 sentence direct response.
• Answers include caveats for compatibility, persistence, and benchmark scope.
• FAQ hub is internally linked from product page and major articles.