Add logic to instrument AWS Lambda functions using Application Signals

[AsakerMohd]

Description of changes:
This is a big change that includes multiple important things to support AWS Lambda function instrumentation:

1. Added our own custom logger: This removes dependency on Microsoft.Extensions.Logging.Console since it's net core specific. This improves the net6 and net8 support.
2. Added lambda sample app with terraform and a deployment script that builds the lambda layer and deploys it with the app and an API gateway.
3. The main logic is in the LambdaWrapper.cs. This will be the main entry point as the handler. It will then call the original lambda handler and then calls forceFlush. This ensures that traces are flushed when the Lambda function finishes execution. This also includes updates to the instrument.sh script. When setting the special lambda env var AWS_LAMBDA_EXEC_WRAPPER=/opt/instrument.sh, the lambda runtime executes this script to add OTEL specific env vars to instrument the function.

Testing:
Tested by running the build-and-deploy.sh. This deployed the sample app and the lambda layer. After executing the lambda layer, the traces were visible in both the xray console and the application signals console.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.