Feat/e2e judicial workflow test suite

[Nareshkumawat-star]

Pull Request: End-to-End Judicial Workflow Test Suite

Description

This PR introduces a comprehensive End-to-End (E2E) & Integration Test Suite covering the critical judicial workflow:

1. Stage 1: Litigant creates account -> files a case -> sees case in dashboard.
2. Stage 2: Lawyer accepts case assignment -> views case documents.
3. Stage 3: Judge claims case -> schedules hearing -> issues summons.
4. Stage 4: Judge delivers judgment -> case status transitions to CLOSED.
5. Stage 5: Litigant receives notification -> views judgment on case detail page.

Issue Resolved

Closes #1630

Type of Change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

Changes Included

• backend/nyaysetu-backend/src/test/resources/application-test.properties: Created dedicated test profile for in-memory DB testing.
• backend/nyaysetu-backend/src/test/java/com/nyaysetu/backend/integration/JudicialWorkflowIntegrationTest.java: Implemented MockMvc integration tests for multi-role judicial flow.
• frontend/nyaysetu-frontend/playwright.config.js: Playwright browser configuration.
• frontend/nyaysetu-frontend/e2e/judicial-workflow.spec.js: Frontend E2E Playwright test spec.
• frontend/nyaysetu-frontend/package.json: Added @playwright/test devDependency and test:e2e npm script.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[vercel]

Someone 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 @Nareshkumawat-star, 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! 🚀