fix(dashboard): correct user extraction from ApiResponse in login flow

The frontend was incorrectly referencing response.data.user instead of response.data.data.user after a recent backend response format change using ApiResponse. This caused the login and auth check to fail, resulting in immediate redirects back to the login page.

Author: yash-pouranik

apps/web-dashboard/src/context/AuthContext.jsx

@@ -12,7 +12,7 @@ export const AuthProvider = ({ children }) => {
             try {
                 const response = await api.get('/api/auth/me');
                 if (response.data.success) {
-                    setUser(response.data.user);
+                    setUser(response.data.data.user);
                 }
             } catch (err) {
                 console.error("Not authenticated:", err.message);

apps/web-dashboard/src/pages/Login.jsx

@@ -67,7 +67,7 @@ function Login() {
       const response = await api.post('/api/auth/login', formData);
 
       if (response.data.success) {
-        login(response.data.user);
+        login(response.data.data.user);
         toast.dismiss(loadingToast);
         toast.success('Welcome back.');
         navigate('/dashboard');

apps/web-dashboard/src/pages/OtpVerification.jsx

@@ -58,7 +58,7 @@ function OtpVerification() {
             toast.success('Email verified successfully!');
 
             if (res.data.success) {
-                login(res.data.user);
+                login(res.data.data.user);
             }
             navigate('/dashboard');
         } catch (err) {