Fix: Lambda Topology Issue

[yiyuan-he]

Issue #, if available:
Lambda Topology issue -- PRs in other ADOT SDKs:

• Fix: Lambda Topology Issue aws-otel-python-instrumentation#319
• Fix: Lambda Topology Issue aws-otel-js-instrumentation#149
• Fix: Lambda Topology Issue aws-otel-java-instrumentation#1016

Description of changes:

• Apply fix for the Lambda Topology issue. The logic mimics the fix in our other ADOT SDKs.
• Adding AWS Resource support for Lambda.

Test plan:
Set up two Lambda functions with .NET runtimes and tested with custom Lambda layer with fix built-in. Below are screenshots of the topology for various configurations.

We observe the following correct behaviors for topology above:

• Service entity node for Invoke call to downstream lambda.
• AWS Resource node for GetFunction call to downstream lambda.
• AWS Resource node for ListBuckets call to downstream s3.

We observe the following correct behaviors for topology above:

• Downstream lambda called with Invoke is correctly treated as RemoteService entity when not instrumented

We observe the following correct behaviors for topology above:

• Two different downstream Lambdas can be distinguished even if they are both RemoteService entity type nodes.

Validated that the correct trace is generated for lambda instrumentation patch. This trace is for GetFunction call.

I could not validate Invoke directly since the .NET sample app sends the traces to CloudWatch via EC2 instance which conflicts with the Lambda environment. However, the above Topology behaviors and EMF Logs are sufficient to confirm the intended behavior.

Invoke EMF Logs

{
    "Lambda.Function.Name": "lambdaA",
    "RemoteOperation": "Invoke",
    "RemoteEnvironment": "lambda:default",
    "Service": "lambdaA",
    ...
    "RemoteService": "lambdaB",
    "Telemetry.SDK": "opentelemetry,1.6.0.dev0-aws,dotnet,Auto",
    "Environment": "lambda:default",
    "aws.log.group.names": "/aws/lambda/lambdaA",
    "PlatformType": "AWS::Lambda"
}

GetFunction EMF Logs

{
    "Lambda.Function.Name": "lambdaA",
    "RemoteOperation": "GetFunction",
    "Service": "lambdaA",
    ...
    "RemoteService": "AWS::Lambda",
    "RemoteResourceIdentifier": "lambdaB",
    "Telemetry.SDK": "opentelemetry,1.6.0.dev0-aws,dotnet,Auto",
    "Environment": "lambda:default",
    "aws.log.group.names": "/aws/lambda/lambdaA",
    "PlatformType": "AWS::Lambda",
    "RemoteResourceType": "AWS::Lambda::Function"
}

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