Add stacktraces to Lambda logs

[mtfranchetto]

Description

Print the complete stacktrace when logging an error on CW.

Although it's not ideal to have each stacktrace entry on a separate line (and I thought this was an issue) it's actually the behavior of the Python Lambda runtime, and cannot be changed (more details here). This can behavior can be overcome by going through Logs Insights first to find the log stream and time of the error, then visiting the full log stream to see the stacktrace.

How Has This Been Tested?

References

PR Quality Checklist

• [x] I added tests to new or existing code
• [] I removed hardcoded strings and used our i18n solution instead (see here)
• [ ] I made sure no sensitive info gets logged at any time in the codebase (see here) (e.g. no user info or details, no stacktraces, etc.)
• [ ] I checked that infrastructure/update_infrastructure.sh runs without any error
• [ ] I checked that npm run build builds without any error
• [x] I checked that clusters are listed correctly
• [ ] I checked that a new cluster can be created (config is produced and dry run passes)
• [ ] I checked that login and logout work as expected

In order to increase the likelihood of your contribution being accepted, please make sure you have read both the Contributing Guidelines and the Project Guidelines

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[mtfranchetto]

Approved, the only thing I would keep in mind is that, if running still in an except clause, we could use logger.error again and print info about a previously caught exception even if that's not the intention

Makes sense, but this case is not that relevant to change the implementation right now. By the way, let's keep an eye and, if that happens, let's figure out how to change the logger.