Added route-level error boundaries and fallback UI

[Devangee20]

Pull Request

Description

Added route-level ErrorBoundary wrappers for important dashboard pages to prevent the entire application from crashing when a single route fails. Implemented isolated error handling for:

Litigant routes
Lawyer routes
Judge routes

Wrapped critical pages with ErrorBoundary components so fallback UI is shown only for the affected page. -->
Closes #314

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

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]

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

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nyaysetu	Ready	Preview, Comment	May 17, 2026 1:34pm

[viru0909-dev]

@Devangee20 Please write a detailed description.