Add Full Request Parameters for API Calls in Logs When Server Encounters 500 Errors

[alexskr]

Currently, when the server encounters a 500 error, the logs do not include the full request parameters for API calls, especially for POST requests. This makes it challenging to troubleshoot and reproduce issues, as essential details about the request are missing from the logs.

Request:
Enhance the logging mechanism to include full request parameters for all API calls when a 500 error occurs.
This should capture the request body, query parameters, headers, and other relevant information that would be useful for debugging. Ensure that sensitive data (e.g. API keys) are masked or redacted to avoid exposing sensitive information in the logs.