Add cloud deployment support: Vercel (frontend) + Render (backend)

[Copilot]

The Angular frontend and Express/TypeScript backend lacked any cloud deployment configuration. This PR wires up one-click deployments for both, without requiring a separate repository for the backend.

Frontend → Vercel (client-ng/)

• vercel.json — build command, output dir (dist/client-ng/browser), SPA rewrites, long-lived cache headers for hashed assets
• scripts/set-env.mjs — generates environment.prod.ts from API_URL env var before ng build; falls back to /api for Docker/Nginx mode
• package.json — new build:prod script: node scripts/set-env.mjs && ng build --configuration=production

Vercel build pipeline:
  npm run build:prod
    └─ set-env.mjs reads API_URL → writes environment.prod.ts
    └─ ng build --configuration=production (bundles with injected API URL)

Backend → Render (render.yaml at repo root)

Render supports monorepos via rootDir — no separate repo needed.

• render.yaml — Render Blueprint defining rootDir: server-v2, build/start commands, /api/version health check, JWT_SECRET auto-generated, MONGODB_URI and CORS_ORIGINS as dashboard-only secrets (sync: false)

services:
  - type: web
    rootDir: server-v2
    buildCommand: npm ci && npm run build
    startCommand: npm start
    healthCheckPath: /api/version
    envVars:
      - key: JWT_SECRET
        generateValue: true
      - key: MONGODB_URI
        sync: false
      - key: CORS_ORIGINS
        sync: false

Documentation

• docs/deployment-render.md — MongoDB Atlas setup, Blueprint vs manual dashboard deployment, Vercel↔Render wiring, free tier caveats
• docs/deployment-vercel.md — updated Step 1 to reference the Render guide
• README.md — added quick-reference tables for both platforms with links to full guides

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.