feat: add Weekly Developer Progress Summary Dashboard (#2715)

[desireddymohithreddy0925]

Description

Resolves #2715

Introduces a Weekly Progress Summary Dashboard that provides a consolidated view of a user's activity over the last 7 days. This helps developers easily track their progress and understand their contribution trends over time without needing to manually interpret different sections.

Changes Made

• API Enhancements: Expanded /api/metrics/weekly-summary to aggregate GitHub Issues alongside Commits and PRs. It also now returns a 7-day array of daily commits and a breakdown of repositories contributed to.
• New Dashboard Widget: Added the <WeeklyProgressSummary /> component to the dashboard. It features key metrics with weekly trend comparisons, a recharts activity trend graph, and a repository progress breakdown.
• Export to PDF: Added a "Download PDF" feature allowing users to export their weekly summary instantly.

Acceptance Criteria

• A Weekly Progress Summary section is added to the dashboard.
• Users can view commits, pull requests, and issues from the last 7 days.
• Weekly contribution trends are displayed using charts.
• Repository-wise contribution breakdown is available.
• The dashboard is responsive across desktop and mobile devices.
• UI follows existing DevTrack design guidelines.

[github-actions]

GSSoC Label Checklist 🏷️

@Umbrella-io — 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 contribution! We are currently in a code cleanup sprint and not accepting new features. Please see the discussion for details: #2651

This PR will be revisited once the sprint ends. In the meantime, contributions to testing, refactoring, bug fixes, or documentation are welcome.