Fix#215 API versioning

[iGEORGE17]

Summary

Introduces URL-based API versioning by routing all existing endpoints under /v1/. Unversioned paths issue a 301 Moved Permanently redirect to their /v1/ counterpart, preserving backward compatibility for existing clients.

---

Changes

Core

• Enabled VersioningType.URI with defaultVersion: '1' in main.ts

Controllers

• Updated all controllers — @Controller({ path: '', version: '1' })

Docs

• Added VERSIONING.md with migration guide and instructions for adding future versions

---

Endpoint Mapping

Old	New	Status
GET /creators	GET /v1/creators	301 redirect
GET /creators/:id	GET /v1/creators/:id	301 redirect
POST /creators	POST /v1/creators	301 redirect
PUT /creators/:id	PUT /v1/creators/:id	301 redirect
DELETE /creators/:id	DELETE /v1/creators/:id	301 redirect
GET /users	GET /v1/users	301 redirect
GET /users/:id	GET /v1/users/:id	301 redirect
POST /users	POST /v1/users	301 redirect
PUT /users/:id	PUT /v1/users/:id	301 redirect
DELETE /users/:id	DELETE /v1/users/:id	301 redirect

How to Add a Future Version

No changes to v1 are required. Create a new controller with version: '2' and register it in the module:

@Controller({ path: 'creators', version: '2' })
export class CreatorsV2Controller { ... }

Closes #215

[aji70]

lfg