feat: enforce API versioning with /v1 prefix

[Agbasimere]

Closes: #388

Description

This PR introduces API versioning to future-proof our internal routes against breaking contract changes by enforcing a /v1 prefix across all endpoints.

To ensure a seamless transition without disrupting existing clients, a server-level rewrite rule was implemented alongside the core restructuring process.

Changes Included

• Route Restructuring: Moved all existing routes physically from src/app/api/ into src/app/api/v1/.
• Backward Compatibility: Introduced a rewrite mapping inside next.config.ts (/api/:path((?!v1/).*) -> /api/v1/:path) to silently route legacy unversioned requests to /v1.
• Internal Migration: Updated all explicit internal fetch operations throughout hooks, components, and utility classes to target the new /api/v1/ schema.
• Swagger Alignments: Pointed swagger-config.ts definitions globally to match /api/v1/ routing.
• Test Suites updated: Updated descriptive aliases inside .test.ts files to reflect the updated endpoints.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Verified legacy /api/login rewrites gracefully to /api/v1/login using Next's rewrite rules.
• Validated Swagger documentation still loads and discovers routes.
• Executed unit tests over /v1/ endpoints.

[codeZe-us]

@Agbasimere this is okay

[codeZe-us]

@Agbasimere please resolve conflicts

[Agbasimere]

@codeZe-us resolved.