telemetry(amazonq): attach stack trace in onCodeGeneration failures

[siakmun-aws]

Problem

To further find issues in onCodeGeneration, need to attach stack trace when sending metrics

Solution

Attach stack trace when sending metrics

---

• Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
• Your code changes must meet the guidelines in CONTRIBUTING.md.
• License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[justinmk3]

This is lacking an acceptable explanation of what the purpose is, and how it works. Did you test this with a production webpack'd build? Nodejs stacktraces in the production build are usually obfuscated.

The docstring of the function does not give useful insights.

The function is non-trivial, and has no test coverage.

Assuming the function works, it belongs in a core util module, not randomly in the middle of a feature module.