FOUR-31810 Only output stack traces for debug logs

[nolanpro]

Issue & Reproduction Steps

Logs have too much info and they are taking up a ton of space

Requires

• https://github.com/ProcessMaker/connector-send-email/pull/369
• https://github.com/ProcessMaker/connector-slack/pull/54

ci:connector-send-email:task/FOUR-31810
ci:connector-slack:task/FOUR-31810

Solution

• Only output traces when log level is debug

How to Test

https://processmaker.atlassian.net/browse/FOUR-31810

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-31810

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[julceslauhub]

Approved