perf(database): optimize N+1 query problem in case fetching

[Nikhil-0710]

Summary

Closes #831

Optimized the case fetching mechanism by implementing JOIN FETCH in CaseRepository to eagerly load associated documents. This eliminates the N+1 query problem where the application was executing redundant database calls for every case to retrieve its documents.

Implementation Details

• Added findAllWithDocuments() method to CaseRepository.java.
• Used JPQL LEFT JOIN FETCH c.documents to ensure cases and documents are retrieved in a single optimized database transaction.
• This change will significantly reduce database load as the number of cases and documents grows.

Testing

• Verified compilation success (mvn clean compile).
• Code follows project naming conventions.
• Validated that existing repository methods remain functional.

Checklist

• Code follows the project's style guide.
• No unrelated files are included in this PR.
• Commit message follows Conventional Commits format.
• PR is targeting the correct base branch (main).

[vercel]

@Nikhil-0710 is attempting to deploy a commit to the CodeBlooded's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Hi @Nikhil-0710, thanks for contributing to Nyay Setu! 🎉

I have automatically:

• 👤 Assigned this PR to you.
• 🏷️ Applied the gssoc:approved label.

Our workflows will now analyze your changes to classify:

• 📈 PR Difficulty: level:*
• 🧩 PR Type: type:*
• 🌟 PR Quality: quality:*

Tip

Ensure your PR description references the issue it resolves (e.g. Closes #123). This allows the bot to inherit any additional labels from that issue!

Happy coding! 🚀