As a user, I do not want to see stacktraces when errors occur

[frankinspace]

Not urgent as we are still in development but I want to track this because we need to fix it before public deployment.

The default error page currently includes stack traces and info that we do not want to be publicly available when the service is published.

Need to create a user-friendly error page that indicates an error occurred. The error page should include a unique error code identifier so that service operators/developers can quickly search application logs using the unique error code to find the relevant stack trace.

[viviant100]

• Approach: Generate an UUID and log the error information associated with it.
• Use Case: If the user reports the error UUID, we can use it as an index to search the logs and retrieve the actual stack trace on the back end.
• Note: The stack trace should be recorded in the application logs and not displayed to the end user.