test(api/user-details): Enhance Hydration Stability and Error Handling

[anshika1179]

Description

Fixes #6813

Implemented complete Hydration Stability, Exception Safety & Error Fallbacks testing (app/api/user-details/route.error-resilience.test.ts) for the user-details API route.

The testing suite verifies the API resilience through:

1. Handling missing username gracefully.
2. Handling invalid username format gracefully.
3. Returning 404 when user is not found.
4. Handling unexpected server errors gracefully.
5. Returning partial data when fetchGitHubContributions throws a transient error.

Pillar

• Other (Bug fix, refactoring, docs)

Visual Preview

N/A (Test addition)

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have updated README.md if I added a new theme or URL parameter.
• I have started the repo.
• I have made sure that i have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[vercel]

@anshika1179 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[retenta-bot]

This pull request implements critical testing for the user-details API route, ensuring it handles various error scenarios gracefully. This aligns with previous decisions to enhance the robustness of the API, particularly in responsive contexts. Great work on this! Looking forward to your contributions in the future.

[github-actions]

🚨 Hey @anshika1179, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪