user can now verify email with code on 2fa using alternate context when creating an account

[Shazzz135]

This pull request implements email verification as part of the signup flow, enhances backend and frontend logic to support this, and introduces protected dashboard routes that require both authentication and verified email. The changes include backend support for email verification templates, improved user data handling, and frontend updates for signup, verification, and dashboard access.

Backend changes for email verification:

• Added a new email template system for signup verification, including subject, HTML, plain text, and preview files (signupVerification templates and related data mapping). [1] [2] [3] [4] [5]
• Refactored EmailService.sendVerificationCode to use the new template manager for rendering email verification messages.

User data enhancements:

• Included isEmailVerified in user objects returned by login, registration, and profile endpoints to allow the frontend to check email verification status. [1] [2] [3]

Frontend signup and verification flow:

• Updated SignupForm to redirect users to a two-factor authentication (2FA) page for email verification after registration, storing relevant data in sessionStorage.
• Enhanced TwoFactorAuth to handle both password reset and signup verification flows, including verifying email, updating tokens, fetching user data, and redirecting to the appropriate dashboard. [1] [2] [3] [4] [5] [6]
• Added an EmailVerificationSuccess component to display a confirmation screen and redirect users to their dashboard after successful email verification.

Protected dashboard routes:

• Introduced a ProtectedRoute component to restrict access to dashboard routes, requiring both authentication and verified email status. Updated dashboard routes in App.tsx to use this protection. [1] [2] [3] [4]

[Flapjacck]

LGTM