feat: enhance API route naming conventions and structure

- Added comprehensive guidelines for API route naming and structure in `ROUTE_NAMING_BEST_PRACTICES.md`.
- Updated `ARCHITECHTURE.md` to reference the new best practices document.
- Refactored course-related routes to follow new naming conventions, including changes to endpoint paths and validation schemas.
- Removed the deprecated course clone route and integrated cloning functionality directly into the course routes.
- Adjusted various API methods to ensure consistent usage of HTTP methods and parameter structures across the application.

apps/api/src/routes/dash/stats.ts

@@ -5,17 +5,17 @@ import { getOrganisationAnalytics } from '@api/services/dash';
 import { handleError } from '@api/utils/errors';
 import { zValidator } from '@hono/zod-validator';
 
-export const dashAnalyticsRouter = new Hono().post(
+export const dashAnalyticsRouter = new Hono().get(
   '/stats',
   authMiddleware,
-  zValidator('json', ZDashStats),
+  zValidator('query', ZDashStats),
   async (c) => {
     try {
-      const { orgId, siteName } = c.req.valid('json');
+      const { orgId, siteName } = c.req.valid('query');
 
       const result = await getOrganisationAnalytics(orgId, siteName);
 
-      return c.json({ success: true, data: result }, 201);
+      return c.json({ success: true, data: result }, 200);
     } catch (error) {
       return handleError(c, error, 'Failed to load organisation analytics');
     }