Capture and handle errors during stringify.

[purple4reina]

What does this PR do?

When the response object contains a circular reference, JSON.stringify will throw an error. This should be caught and ignored.

Motivation

Fixes https://github.com/DataDog/datadog-lambda-js/issues/541

Testing Guidelines

Additional Notes

Types of Changes

• [ ] Bug fix
• [ ] New feature
• [ ] Breaking change
• [ ] Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

• [ ] This PR's description is comprehensive
• [ ] This PR contains breaking changes that are documented in the description
• [ ] This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
• [ ] This PR impacts documentation, and it has been updated (or a ticket has been logged)
• [ ] This PR's changes are covered by the automated tests
• [ ] This PR collects user input/sensitive content into Datadog
• [ ] This PR passes the integration tests (ask a Datadog member to run the tests)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.03%. Comparing base (78c1900) to head (6b1cf37). Report is 13 commits behind head on main.

:exclamation: Current head 6b1cf37 differs from pull request most recent head 143da60. Consider uploading reports for the commit 143da60 to get more accurate results

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #544 +/- ## ========================================== + Coverage 81.75% 82.03% +0.28% ========================================== Files 54 56 +2 Lines 2209 2305 +96 Branches 515 533 +18 ========================================== + Hits 1806 1891 +85 - Misses 337 343 +6 - Partials 66 71 +5 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[rdsedmundo]

@purple4reina thanks for handling this.

Is there a timeline for when this would be released as a new layer? It'd be nice to have this bugfix in our side because we are stuck with an old version of the layer due to this.