fix(metrics): include GraphQL discussion activity in engagement score

[nyxsky404]

Summary

/api/metrics/devtrack-badges always returned discussions.count/points: 0 because the score used a hardcoded placeholder. This wires up the same GraphQL contributionsCollection fields used by /api/metrics/discussions (discussion + discussion-comment counts for the last 30 days) and folds them into the weighted breakdown (* 2, capped at 15). GraphQL failures soft-fail to 0 so the rest of the score still returns.

Closes #3352

---

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

• Added GraphQL discussion contribution fetch in src/app/api/metrics/devtrack-badges/route.ts
• Included real discussion count/points in the community engagement breakdown
• Added unit coverage for users with activity, without activity, and GraphQL failure

---

How to Test

1. Sign in with a GitHub account that has discussion or discussion-comment activity in the last 30 days
2. Call GET /api/metrics/devtrack-badges
3. Confirm breakdown.discussions.count and points are non-zero and total includes those points
4. For an account with no discussion activity, confirm discussions stay at 0 while other categories still populate

Expected result:

Discussions reflect real GitHub contribution data instead of a permanent zero placeholder.

---

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

---

Additional Context

Weight matches issuesOpened (count * 2, max 15). Overall score still clamps to 100.

Made with Cursor

[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

[nyxsky404]

@Priyanshu-byte-coder please review pr and merge it, i have also fixed the ci failures

[nyxsky404]

Hi @Priyanshu-byte-coder — gentle nudge.

This PR is ready for review from my side. I've rebased/kept it current where possible. If CI is red due to unrelated upstream/main issues or deploy previews, the code change itself should still be reviewable.

Please review and merge when you can — and add gssoc:approved (+ difficulty/type) if appropriate so it can count for GSSoC.

Thank you!