fix(fetchUserInfo): add graceful fallback for live LeetCode API failures

[Yashaswini-K-P]

Description

Makes the external LeetCode API fetch in fetchUserInfo graceful and optional. Previously, non-200 status codes (like 500 or 429) caused unhandled errors that crashed the entire data-fetching flow, preventing users from viewing cached history and badges.

Linked Issue

Fixes #352

Changes Made

• Added a local .catch() error handler to livePromise to gracefully catch and log external API failures.
• Prevented errors from propagating to ensure the function safely falls back to repository data instead of crashing.

Type of Change

• Bug fix
• New feature
• UI/Visual update
• Documentation update
• Refactor

Testing

• Tested locally
• Tested on mobile viewport (if applicable)
• No console errors introduced

Checklist

• My code follows the project's coding style
• I have formatted my code locally by running npx prettier --write . before submitting
• I am submitting my PR from a dedicated feature/* branch, not the main branch
• I have performed a self-review of my code
• My changes generate no new warnings or errors
• I have updated documentation if required
• I have linked the relevant issue

Screenshots / Screen Recording

[github-actions]

Thank you for submitting a pull request.

Please ensure your changes comply with the project's contribution guidelines and that all workflow checks pass successfully.

Formatting and Branching

• Please confirm you have formatted your code locally using npx prettier --write . before requesting a review.
• Ensure this PR is made from a feature/* branch and not main.

Note: This project is currently maintained by a solo maintainer, so reviews and responses may sometimes take a little time. Thanks for your patience.