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.

packages/email/src/config/env.ts

@@ -1,4 +1,4 @@
-import { z } from 'zod';
+import * as z from 'zod';
 
 const envSchema = z.object({
   SMTP_HOST: z.string().optional(),

packages/email/src/emails/invite-teacher.ts

@@ -1,4 +1,5 @@
-import { z } from 'zod';
+import * as z from 'zod';
+
 import { defineEmail } from '../send';
 import { getDefaultTemplate } from '../templates';
 
@@ -23,4 +24,3 @@ export const inviteTeacherEmail = defineEmail({
     return getDefaultTemplate(content);
   }
 });
-