Backend: Implement environment variables validation using dotenv and Zod #4

📁 Implementation Directory

backend/src/config/env.ts

🎯 Goal

Ensure all required environment variables are present and valid at startup.

📋 Requirements

• Load .env via dotenv.\n- Validate variables using Zod schemas.\n- Fail fast if config is invalid.

🔧 Technical Scope

• Node.js / Express
• TypeScript
• MongoDB / Mongoose
• Stellar Soroban RPC

🌿 Branch

git checkout -b feat/env-validation

✅ Acceptance Criteria

• Using an AI Agent to submit a PR is DISALLOWED.
• Strict Layered Architecture (Non-Negotiable): Implement using the Controller -> Service -> Model pattern.
• Data Source: Response data must be retrieved from the database. No Inline Mock Objects or Hardcoded Values usage for integration.
• Environment: Contributors must use the requested .env credentials to enable implementation with real-life data.
• API Versioning: API Must Be Versioned (e.g., /api/v1/...).
• Production Ready: Code must look production-ready (robust error handling, strong typings).
• Proof of Work: Upload a screenshot of work done (i.e., API Response Success via Postman/Browser, or all unit tests passed successfully).
• PR Content: Must include Closes #[issue_id] with a work done summary.

📌 PR Requirements

• ⚠️ Assignment required before starting — comment on this issue to request assignment.
• PR must comply fully with the CONTRIBUTING.md.
• AI Agent submissions are DISALLOWED and will be closed without review.
• No Inline Mock Objects or Hardcoded Values usage for integration.