token support

[andyli11]

Feature

Below is the code from the api-construct file in the RT CDK. Identify sources are both x-api-key and Authorization.

        // Add custom authorizer
        const lambdaAuthorizer = new apigw.RequestAuthorizer(this, 'LambdaAuthorizer', {
            handler: lambdaAuthorizerFn,
            identitySources: [apigw.IdentitySource.header('x-api-key'), apigw.IdentitySource.header('Authorization')],
        });

After testing and reviewing AWS docs, ALL identity sources must be present in the request header.

For more details, see: https://stackoverflow.com/questions/76789499/api-gateway-multiple-identity-sources

Tested

• on both async and sync requests on the DEV account using DEV api key
• DEV endpoint: https://ntbetrrbe2.execute-api.us-west-2.amazonaws.com/v1

NOTES:

• ChatGPT says that only one of x-api-key and Authorization need to be in the header to pass but that is INCORRECT and disproven through AWS docs and testing.
• Build failed because changes are associated with RT CDK pr.

[CambioML]

Let's fix the linter.