[BUG] Resolve SerpAPI "required vs optional" mismatch across backend, frontend, and docs

[EQuBitC18]

Description

The current project treats API key requirements inconsistently:

-> backend keys-status reports openai and serpapi as required
-> frontend modal logic blocks when SerpAPI is missing
-> docs and .env.example describe SerpAPI as optional in some places
-> generation logic can run without SerpAPI by skipping web search context

This creates a confusing reliability problem for first-time local setup.

Steps to Reproduce

Start frontend and backend without SERPAPI_API_KEY.
Open app and check API key modal behavior.
Compare modal requirement with backend generation behavior and docs.
Observe that generation can run without SerpAPI, while UI/docs may still treat it as required.

Expected Behavior

API key requirements should be consistent across backend, frontend, and docs, with only truly required keys blocking normal usage.

Severity

Low (Minor inconvenience)

Version

No response

Environment

No response

Additional Context

Required list in backend response: Tezrisat_Backend/api/views.py:63
Modal enforcement logic: Tezrisat_Frontend/tezrisat_frontend/src/components/AppLayout.tsx
Setup docs key guidance: docs/setup.md

Checklist

• I have searched for similar issues and confirmed this is not a duplicate
• I have tested this on the latest version
• I am willing to provide additional information if needed