Support for using Lambda arm architecture.

[judetrimble]

Describe what happened:

• Changed the lambda architecture

Describe what you expected:

• no data in datadog
• error in cloudwatch logs,
  -[ERROR] Runtime.ImportModuleError: Unable to import module 'lambda_function': No module named 'ddtrace.internal._encoding'
  Traceback (most recent call last):

LAMBDA_WARNING: Unhandled exception. The most likely cause is an issue in the function code. However, in rare cases, a Lambda runtime update can cause unexpected function behavior. For functions using managed runtimes, runtime updates can be triggered by a function change, or can be applied automatically. To determine if the runtime has been updated, check the runtime version in the INIT_START log entry. If this error correlates with a change in the runtime version, you may be able to mitigate this error by temporarily rolling back to the previous runtime version. For more information, see https://docs.aws.amazon.com/lambda/latest/dg/runtimes-update.html

Steps to reproduce the issue:

• create the lambda function, change its architecture to use arm.

[tpk7548]

"AWS Lambda functions running on Graviton2, using an Arm-based processor architecture designed by AWS, deliver up to 34% better price performance compared to functions running on x86 processors." - this is a quote from the current AWS Lambda pricing page (https://aws.amazon.com/lambda/pricing/).

[GdahRATP]

i am using terraform to create the lambda function and in terraform you can only specify the runtime not the version of the runtime. so the only solution is to update your code to use the newest and the latest runtime of aws