feat: Improve GUI Crash Page with Detailed Error Information

[aryanranderiya]

Description:

The current GUI crash page provides minimal information, making debugging difficult. To enhance developer experience and troubleshooting efficiency, the crash page should display:

Error Message: Clearly state what went wrong. Error Name: Provide the specific error type for quick identification. Component Call Stack: Show where the error originated in the React component hierarchy.

Currently, developers have to open the browser console, sift through multiple error logs, and scroll through several messages just to understand the root cause. This feature will reduce debugging time by presenting critical information directly on the error page.

Steps to reproduce:

1. Trigger an error in the Rocket.Chat UI (e.g., by introducing a deliberate error in a component).
2. Observe the current crash page, which lacks detailed information.
3. Open the browser console and manually scroll through logs to find the actual error message.

Expected behavior:

Actual behavior:

Server Setup Information:

• Version of Rocket.Chat Server: 7.5.0 develop
• License Type:
• Number of Users:
• Operating System: Ubuntu 24.04
• Deployment Method:
• Number of Running Instances: 1
• NodeJS Version: 22.13.1
• MongoDB Version:

Client Setup Information

• Desktop App or Browser Version: Google Chrome 134.0.6998.89 (Official Build) (64-bit)
• Operating System: Windows 10 Version 22H2 (Build 19045.5608)

Additional context

I have finished working on this, will create a Pull Request soon.

[MartinSchoeler]

Please use the correct repository for feature requests, moving this issue.