Summary

Standarizes the way error are being logged.

Closes #555.

Steps to test

• Run kubectl get pods | grep goal-error-log-minds-app and take not of the Pod Name.
• Run kubectl logs -f <Pod Name>
• Check for uncaught errors (those that triggers a 500) output in the logs, they should be displayed correctly and with its full trace in a single line.

Note: Xander might not be able to test this, so maybe we should defer QA verification to Mark or Brian.

Estimated Regression Scope

Error logging might be skewed or Sentry reporting for uncaught error might not be triggering.