FT-800 Added better message logging for unhandled exceptions

[pavanmanish-atlan]

Change description

• This update improves exception handling by enhancing the error response to provide more meaningful information for developers.
• Instead of a generic error message, the response now includes a detailed stack trace analysis, offering insights into the specific cause of the error.

Type of change

• Bug fix (fixes an issue)
• New feature (adds functionality)

Related issues

Fix FT-800 , PLT-2791

Test Cases

1. Test Case 1: Single exception

   • Input: IllegalArgumentException("Invalid argument provided")
   • Expected Output: JSON with exception type, message, and location.

2. Test Case 2: Exception with a cause

   • Input: IllegalStateException("Illegal state occurred") with NullPointerException as cause
   • Expected Output: JSON with both exceptions and their details.

3. Test Case 3: Exception with no message

   • Input: RuntimeException()
   • Expected Output: JSON with default message "No additional information provided."

4. Test Case 4: Exception with empty stack trace

   • Input: RuntimeException("Runtime exception occurred") with empty stack trace
   • Expected Output: JSON with "Unavailable" as location.

5. Test Case 5: Circular cause

   • Input: IllegalArgumentException("Self-causation not permitted") causing itself
   • Expected Output: JSON indicating circular reference detected.

6. Test Case 6: Null exception

   • Input: null
   • Expected Output: JSON with "No exception provided" message and empty causes list.

Checklists

Development

• Lint rules pass locally
• Application changes have been tested thoroughly
• Automated tests covering modified code pass

Security

• Security impact of change has been considered
• Code follows company security practices and guidelines

Code review

• Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
• "Ready for review" label attached and reviewers assigned
• Changes have been reviewed by at least one other contributor
• Pull request linked to task tracker where applicable