Motivation

When running a new test in Events v2 with APIGW NG enabled, I've encountered test failures due to bad replacement in the snapshots (it would replace the HTTP value across the whole snapshot string, leading to very weird error in ResponseMetadata), see the run here: https://app.circleci.com/pipelines/github/localstack/localstack/28547/workflows/b21fae5b-918f-4356-8a18-51b324914127/jobs/249483

I've refactored the snapshot logic a bit in order to delete less information from it, for us to be able to validate some assumptions in the requestContext, and have a clear idea of what is wrong/need to be fixed in the snapshot via the skip_verify.

It showed that events will send specific headers to APIGW, like X-Amz-Source-Arn and X-Amz-Source-Account which might be used by the user's API Gateway integration. As a side-note, it also showed events is directly using the Java SDK to send/sign the requests 😄

Changes

• update the transformers to use v1 lambda proxy transform instead of v2
• added snapshot skips instead of transforming the whole problematic payload without replacement
• updated the Python runtime used in the lambda

\cc @cloutierMat