[SVLS-4699] Detect exceptions raised outside of the handler

[TalUsvyatsky]

What does this PR do?

This PR adds telemetry for exceptions that occur outside of the handler function.

When an exception occurs outside of the handler function:

1. aws.lambda.enhanced.errors is emitted
2. A trace with an error span is created

Motivation

• SVLS-4699
• Users should have visibility into this category of errors
• We did the same thing in Python in Detect exceptions raised outside of the handler datadog-lambda-python#475

Testing Guidelines

1. Created a handler file like this for testing "cjs" handler:

  throw new TypeError("im a type error")
  exports.handler = function async (event) {
    const response = {
      statusCode: 200,
      body: JSON.stringify('Hello from Lambda!'),
    };
    return response;
  };

and one like this for testing "mjs" handler:

  throw new TypeError("im a type error")
  export const handler = async (event) => {
    const response = {
      statusCode: 200,
      body: JSON.stringify('Hello from Lambda!'),
    };
    return response;
  };

2. Deployed my function using each handler and invoked it
3. Saw traces with an error span from the call (example trace)
4. Saw aws.lambda.enhanced.errors emitted (graph)
5. Traces appear in serverless detail page invocation table (link to search for function)
6. Issues appear in error tracking and are informative

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 ✅

Project coverage is 82.10%. Comparing base (78c1900) to head (249712e).
Report is 8 commits behind head on main.

❗ Current head 249712e differs from pull request most recent head 75ae1c8. Consider uploading reports for the commit 75ae1c8 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #533      +/-   ##
==========================================
+ Coverage   81.75%   82.10%   +0.35%     
==========================================
  Files          54       56       +2     
  Lines        2209     2286      +77     
  Branches      515      529      +14     
==========================================
+ Hits         1806     1877      +71     
- Misses        337      344       +7     
+ Partials       66       65       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[joeyzhao2018]

I might be wrong but is this fire and forget way of invoking the async method? I'm just wondering if we need to add a.catch(error => { // something like logDebug(error) });

[TalUsvyatsky]

thanks! yes I think you're right, added

[purple4reina]

nit: use camel case wrappedHandler

[purple4reina]

Does js have an append-like function? so we don't have to do the extra allocation.

[duncanista]

Left some comments.

[duncanista]

Why don't we just lazy load everything inside of the condition?

[TalUsvyatsky]

Good idea! Updated