perf: Add SHA1 ETag caching and 304 Status response for Compare API

[MasterJi27]

Resolves #5242. Generates SHA1 ETag for the compare API JSON payload, sets ETag and Cache-Control headers, and returns a 304 Not Modified status response if the client's If-None-Match matches.

[vercel]

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

A member of the Team first needs to authorize it.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Aamod-Dev]

Thanks for the contribution. I went through the changes and the overall approach looks good. The implementation for ETag caching and returning a 304 Not Modified status is clean and correctly includes tests.

Labels Applied:

• \level:intermediate: The PR introduces caching logic via ETag handling for the API endpoint, requiring cross-file updates and understanding of HTTP caching mechanisms.
• \ ype:performance: The primary purpose of this PR is to improve API performance by adding caching.
• \quality:clean: The code is readable, follows project style, and includes comprehensive test coverage for the new caching behavior.
• \mentor:Aamod007\

Once again, great work on this performance optimization!

[github-actions]

🎉 Congratulations @MasterJi27! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨