Log stacktraces in ErrorBoundary

[mendaomn]

Description

This PR adds stacktraces to the log entries coming off the ErrorBoundary

Changes

• log stacktrace and componentStack for errors occurring during component rendering
• log stacktrace for uncaught errors occurring elsewhere

Screenshots

Logs for errors occurring during component rendering

Logs for uncaught errors occurring elsewhere

How Has This Been Tested?

• manually
• unit tests
• deployed and checked on CloudWatch (see screenshots above)

PR Quality Checklist

• [x] I added tests to new or existing code
• [ ] I removed hardcoded strings and used our i18n solution instead (see here)
• [x] 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
• [x] 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.