refactor: extract reusable dashboard API hooks

[Rinki4738]

Summary

Refactored dashboard widget API calls into reusable custom hooks to improve code reusability, consistency, and testability.

Closes #1053

Type of Change

• Refactor / code cleanup

Changes Made

• Added reusable custom hooks:
  • useMetrics
  • useStreak
  • useNotifications
  • useUserSettings
• Moved API fetching logic out of dashboard components
• Standardized loading, error, and data state handling
• Added manual refetch support in hooks
• Updated consuming components to use hooks
• Added TypeScript typings for hook return values
• Added unit tests for all hooks

How to Test

• Run npm install
• Run npm run type-check
• Run npm test
• Optionally run npm run dev and verify dashboard widgets load correctly

Screenshots (if UI change)

No UI changes.

Checklist

• Linked issue in summary
• No TypeScript errors (npm run type-check)
• Self-reviewed the diff
• Added/updated tests if applicable

[vercel]

@Rinki4738 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[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

[github-actions]

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

• Make sure CI is passing (type-check + lint)
• Double-check the PR description is filled out and the issue is linked
• Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

[Priyanshu-byte-coder]

Merge conflict after several PRs landed on main — likely on e2e/landing.spec.js or a shared component. Rebase to unblock:

git fetch origin && git rebase origin/main
# resolve conflicts, then:
git push --force-with-lease

All CI checks look good otherwise — once rebased this is ready to merge.

[Rinki4738]

Rebased with the latest upstream/main changes, resolved merge conflicts, and updated the branch. All tests are passing locally now. Thanks!

[Priyanshu-byte-coder]

The refactor looks good, but adding the repo OAuth scope (giving full repo read/write access) is a breaking change that forces all users to re-authorize. Please remove it unless one of the new hooks explicitly requires it and explain why.

[Rinki4738]

Updated the branch and resolved the related test issues after rebasing. Also removed the unnecessary repo OAuth scope and adjusted the auth tests accordingly. All tests are passing locally now.

[Priyanshu-byte-coder]

This PR has a merge conflict with main. Please rebase your branch and resolve conflicts. Additionally, please review the OAuth scope changes in auth.ts — ensure no unnecessary scopes are being added, and that the existing read:user user:email read:discussion scope configuration is preserved.

[Rinki4738]

Rebased the branch with the latest main changes and resolved the merge conflicts. Also verified that the GitHub OAuth scope remains unchanged (read:user user:email read:discussion) and updated the related auth test mocks accordingly. All tests are passing locally now.

[Priyanshu-byte-coder]

Hi! This PR has been approved (gssoc:approved) but has merge conflicts with the latest main. Please rebase your branch on main, resolve any conflicts, and push — we'll merge right away. Thank you for your contribution!

[Priyanshu-byte-coder]

This PR has 10 merge conflicts with current main — it needs a rebase before it can be merged. The hooks pattern (useMetrics, useStreak, etc.) and the test additions are a great idea. Please rebase and resolve the conflicts.

[Priyanshu-byte-coder]

This PR has conflicts with the current main branch. Please rebase on main to resolve conflicts so it can be reviewed and merged. Run: git fetch upstream main && git rebase upstream/main

[Priyanshu-byte-coder]

This PR now has merge conflicts with main due to recent merges. Please rebase onto the latest main branch and resolve all conflicts to proceed with merging.