fix: resolve duplicate LoginPage declarations, scrambled routing syntax, and missing bcryptjs dependency

[DebasmitaBose0]

Problem

The Next.js client app is currently completely broken and fails to build due to severe TypeScript syntax issues, scrambled routing proxy logics, duplicate default exports, and missing native C++ binary module bindings (bcrypt).

Current Behavior

Running npm run build triggers multiple fatal Turbopack compiler errors:

1. bcrypt cannot be resolved (due to missing native compiler hooks in serverless/windows environments).
2. Duplicated exports of LoginPage in client/app/login/page.tsx.
3. Scrambled routing logic and syntax boundaries inside client/app/api/analyze/route.ts.
4. Mixed parentheses syntax and double-async functions in client/app/dashboard/page.tsx.

Why This Improvement Is Needed

A broken repository build blocks all client deployment and hinders active development. Resolving these syntax and dependency compile issues is absolutely critical to restore production build-safety and allow the suite to function.

Proposed Solution

• Replace native bcrypt with pure-JavaScript bcryptjs which is highly compatible with Next.js Turbopack compilation.
• Clean and de-duplicate client/app/login/page.tsx keeping only the secure, elegant workstation version.
• Re-architect client/app/api/analyze/route.ts to be fully syntax-clean and robust.
• Resolve JSX parentheses blocks and duplicate function definitions inside the dashboard triage panel.

Expected Outcome

• Clean compilation output with zero Turbopack build-time errors.