Improve run.sh developer experience (idempotent venv + prod mode)

[gupta-8]

Problem

run.sh always creates a new venv and always runs uvicorn --reload.
This is inconvenient and not production-friendly.

Proposal

• Make venv creation idempotent (only create if missing).
• Allow toggling reload via env (e.g., RELOAD=1).
• Add a separate run_prod.sh or document production command.

Acceptance Criteria

• Running bash run.sh twice doesn't recreate the venv unnecessarily.
• Reload behavior is configurable.
• README includes dev vs prod commands.

[gupta-8]

Hi @gupta-8, i want to work on this, I'll make a PR

Sure, thanks