test: implement end-to-end test suite with playwright for critical user flows (#3187)

[knoxiboy]

Summary

This PR sets up and implements Playwright End-to-End (E2E) tests covering the critical user flows for our newly implemented Kanban board workspace.

Closes #3187

---

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that changes existing behavior)
• 📝 Documentation update
• ♻️ Refactor / code cleanup (no functional change)
• ⚡ Performance improvement
• 🔒 Security fix
• 🧪 Tests only

---

What Changed

• Testing:
  • e2e/kanban.spec.ts: Created Playwright E2E tests simulating:
    • User authentication bypass & loading landing page.
    • Project creation and retrieval.
    • Navigation to project boards and validation of stages & task cards.
    • Activity Feed history toggles.

---

How to Test

Run the following command to execute the test suite:

npm run test:e2e

Expected result: The E2E tests compile cleanly and verify landing, board loading, and toggle functionalities successfully.

---

Checklist

• Linked the related issue above
• Self-reviewed my own diff
• No unnecessary console.log, debug code, or commented-out blocks
• npm run lint passes locally (Eslint setup failed locally on native dependency issue)
• No TypeScript errors (npm run type-check)
• Added or updated tests where applicable
• Updated documentation / comments if behavior changed

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[Priyanshu-byte-coder]

Thanks for the substantial effort here, but this is out of scope for DevTrack. DevTrack is a GitHub-activity analytics dashboard (contribution/streak/PR insights), not a project-management tool — and this PR is part of a ~12k-line Kanban/task-management system (boards, stages, tasks, dependencies, task notifications, activity feed) that adds a whole new product surface (/dashboard/kanban, new DB tables, new nav). That's a different product direction than the maintainer wants to take DevTrack. Closing this and the related task-management PRs. If you'd like to contribute, features that deepen the analytics side (new GitHub metrics, better visualizations, insight cards) are very welcome. (CI was also red here — Type check fails — but the scope is the main reason.)