feat(milestones): add milestone tracking with progress visualization

[desireddymohithreddy0925]

Summary

This PR introduces milestone tracking with dynamic progress visualization. It allows users to group tasks into high-level milestones with due dates, making sprint planning and project tracking easier directly from the dashboard.

Closes #2886

---

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

• Created src/types/project-milestone.ts to strictly type the new Task and Milestone data models.
• Built a brand new ProjectMilestones component (src/components/ProjectMilestones.tsx) to handle the UI and state management for tracking milestone completion status.
• Added project-milestones to the dashboard widget directory and injected it into the default Goals layout in src/lib/dashboard-layout.ts.
• Implemented dynamic progress bar width updates based on the (completedTasks / totalTasks) * 100 formula.

---

How to Test

1. Navigate to the DevTrack dashboard and ensure the Project Milestones widget is visible (or add it via layout customization).
2. Click "Add Milestone" and create a milestone with a name, optional description, and a due date.
3. In the new milestone card, use the input box to add several tasks (e.g. "Design UI", "Setup API").
4. Click the circle next to tasks to check them off, and verify that the progress bar updates accurately and transitions colors when reaching 100%.

Expected result: The widget allows seamless creation and deletion of milestones and tasks, updating the visual progress bar in real-time as tasks are toggled.

---

Screenshots / Recordings

Before	After
N/A (New Feature)	(Please attach a screenshot of the new milestone widget in action here before submitting)

---

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
• No TypeScript errors (npm run type-check)
• Added or updated tests where applicable
• Updated documentation / comments if behavior changed

---

Accessibility (UI changes only)

• Keyboard navigation works correctly
• Color contrast meets WCAG AA standard
• ARIA labels / roles added where needed
• Tested on mobile / responsive layout

---

Additional Context

Because DevTrack does not currently have a dedicated Tasks database model alongside its core metrics (commits/PRs), this widget leverages localStorage to persist the milestone and task states securely in the client side, allowing it to immediately work for sprint planning without conflicting with the broader goal tracking systems.

[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]

Closing this. It's entangled and partly redundant: (1) it bundles a goal-category feature via add_goal_category migration, which just landed independently in #3194, so that part now conflicts; (2) it also edits src/lib/ssrf-protection.ts and its test, unrelated to milestones; and (3) it was submitted four times under different titles (#3137/#3138/#3139), which is why I'm being strict here. If milestone tracking is something you want to pursue, open a single focused PR that only adds the milestones feature (component + its own migration + types), rebased on current main, and I'll review it on its merits.