feat: include contest data in user info API response

[Yashaswini-K-P]

Description

This PR extends the fetchUserInfo utility function to capture and return the complete contest data object from the upstream LeetCode API wrapper. This allows the backend to expose competitive programming metrics (such as contest rating, global ranking, badges, and percentiles) via the /api/user/:username endpoint, setting up the required data foundation for the frontend profile update.

Linked Issue

Fixes #192

Changes Made

• Updated fetch-user-info.js to initialize and extract the contest data object from liveApiUrl.
• Appended the contest object to the final returned payload of the fetchUserInfo function.
• Added fallback handling (|| null) to ensure graceful execution for users with no contest history.

Type of Change

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

Testing

• Tested locally by starting the server and hitting the /api/user/:username route with an active contest participant's username. Verified that the JSON response now completely returns the nested contest structure containing rating, rank, total participants, top percentage, count, and badge.

• 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 ., or you can simply comment /format on this PR to have our bot do it for you!
• 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.