Issue Description

Currently, when progress data is fetched, we are only sending the userId in the progress object. As a result, the frontend has to make an additional API call to fetch the user data (e.g., username, profile picture). This increases the number of API calls and affects performance. To reduce this, we plan to send the full user data directly with the progress update, eliminating the need for an additional API call on the frontend.

Expected Behavior

• The api response should include the full user data (e.g., username, profile picture) along with the progress object whenever a task's progress is fetched.
• The progress objects will contain the user data alongside the existing progress fields, eliminating the need for the frontend to make a separate API call to fetch user details.
• Ensure compatibility with the frontend, which will render the username and profile picture directly from the progress object without additional API calls.

Current Behavior

• Ccurrently we are only sending userId in the progress object.
• The frontend has to make additional API calls to fetch user details based on the userId for rendering, which increases the number of requests and affects performance.
  simplicity.

Screenshots

Reproducibility

• This issue is reproducible
• This issue is not reproducible

Steps to Reproduce

Severity/Priority

• Critical
• High
• Medium
• Low

Additional Information

Checklist

• I have read and followed the project's code of conduct.
• I have searched for similar issues before creating this one.
• I have provided all the necessary information to understand and reproduce the issue.
• I am willing to contribute to the resolution of this issue.