Include stack trace when logging unexpected errors

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X EE, Master
• Fix Version/s: 7.0.0 DXP FP18, 7.0.0 DXP FP20, 7.0.3 CE GA4, 7.0.0 DXP SP4, 7.0.X EE, 7.0.0 DXP FP37, 7.0.0 DXP SP7, 7.0.5 CE GA6
• Component/s: Core Infrastructure > Log Bridge
• Labels:
  • liferay-digital-enterprise-70-sp4
  • liferay-digital-enterprise-70-sp7
  • liferay-fixpack-de-18-7010
  • liferay-fixpack-de-20-7010
  • liferay-fixpack-de-37-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 4
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/49074

May parts of Liferay have the following code pattern:

try {
}
catch (Exception e) {
    _log.error(e);
}

While it's helpful that we have a _log.error, in many cases, it'd be much more useful if these log messages could contain the stack trace of the exception that was caught.

This ticket aims to capture many of these and log more useful error messages.

Note: This cannot be QA tested, as these are unexpected errors.