feat: Implement Phase 2 cross-cutting services with email and notification enhancements

- Refactor email verification and password reset utilities to use new email service.
- Introduce email delivery queue and notification delivery model for better tracking.
- Enhance file validation and storage services for improved security and ownership management.
- Add cron job for cleaning inactive notifications with retention policy.
- Update document worker to handle document generation and storage more efficiently.
- Implement logging improvements in activity and log workers.
- Create comprehensive documentation for new API endpoints and services.
- Add unit tests for file validation and notification policies to ensure robustness.

app/utils/emailVerification.util.js

@@ -1,7 +1,7 @@
 // app/utils/emailVerification.util.js
 
 const crypto = require("crypto");
-const { sendMail } = require("../utils/mail.util");
+const emailService = require("../services/email/email.service");
 const redis = require("../config/redisClient");
 
 const EMAIL_VERIFICATION_TTL =
@@ -67,19 +67,12 @@ const sendVerificationEmail = async (email, firstName, verificationToken) => {
   const confirmationLink = `${process.env.FRONTEND_URL}/verify-email?token=${verificationToken}`;
 
   // Send email
-  await sendMail({
-    to: email,
-
-    subject: "Confirm Your ZUMRI Account",
-
-    templateName: "emailVerification",
-
-    templateVars: {
+  await emailService.send({
+    recipient: email, templateKey: "emailVerification",
+    variables: {
       customer_name: firstName,
       confirmation_link: confirmationLink,
-    },
-
-    text: `Hello ${firstName}, please verify your ZUMRI account using this link: ${confirmationLink}`,
+    }, eventId: `verify-${hashEmailVerificationToken(verificationToken)}`,
   });
 };