Add API versioning with consistent route structure

[Wilfred007]

What

Routes exist at both /api/ and /api/v1/. The apiVersionMiddleware exists but versioning is not consistently applied. Some routes are duplicated.

Why

Breaking changes will affect existing integrations. Inconsistent versioning makes API evolution impossible.

Scope

In scope: All routes under /api/v1/, /api/ as alias with deprecation header
Out of scope: v2 routes

Acceptance Criteria

• All routes accessible under /api/v1/
• /api/ routes return deprecation warning header
• Version in response header
• No breaking changes to v1

Technical Context

• backend/src/middlewares/apiVersionMiddleware.ts — versioning middleware
• backend/src/routes/v1/ — v1 routes
• backend/src/app.ts — route mounting (both /api/ and /api/v1/)

[guptakumarranjeet150]

Hi maintainers,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Build Add API versioning with consistent route structure with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Testing & Verification: Add component unit tests and ensure zero TypeScript/ESLint warnings.
• Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

Excited to work on this—please assign to me and I'll submit a clean PR shortly!