fix: LambdaProxyIntegrationEventV2 authorizer context

[rishi8094]

Description

The LambdaProxyIntegrationEventV2 does not return custom authorizer contexts in the correct format. Currently, any context data is returned directly within the authorizer object:

{
  "requestContext": {
    "authorizer": {
      "foo": "bar"
    }
  }
}

Instead of being nested in the lambda object:

{
  "requestContext": {
    "authorizer": {
      "lambda": {
        "foo": "bar"
      }
    }
  }
}

Motivation and Context

This change is required as it breaks the local implementation of the custom authorizer.

[dnalborczyk]

thank you for your PR @rishi8094 I have not looked into the details of your PR yet, but you might have to fix the test?

[rishi8094]

thank you for your PR @rishi8094 I have not looked into the details of your PR yet, but you might have to fix the test?

Thank you for taking a look. I have now updated the relevant test case for the proposed fix.

[rishi8094]

@dnalborczyk recently pushed the passing test case, think it's good for a review now.

[rishi8094]

Hey @dnalborczyk, wanted to follow up on this PR.

[casewalker]

Hello! My team is utilizing custom authorizers in Serverless and running locally with serverless-offline, and we have noticed the issue which this PR is setup to fix.

For more context, it appears that AWS uses APIGatewayProxyEventV2WithLambdaAuthorizer for the event-argument of a Lambda behind an Authorizer (seen here), and if you follow the types through their generic arguments, you get to APIGatewayEventRequestContextLambdaAuthorizer, where the actual authorizer's context is in fact wrapped as an object under the lambda key.

Our code will be partially incorrect and more brittle until this PR is merged and released, so I urge you to please merge this at your earliest convenience. Thank you!

[dnalborczyk]

close/re-open in order to run ci.

[dnalborczyk]

thank you @rishi8094