opentelemetry-instrumentation-aws-lambda: Fix aws lambda span creation

[herin049]

Description

Fixes bug where the Lambda invocation Span name would be incorrectly set to the name of the Python handler function instead of the function name. Also fixes an issue where the Lambda invocation Span kind would occasionally not be set to SERVER which violates the OpenTelemetry FaaS semantic conventions.

Fixes #3963

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Unit tests have been updated to reflect changing the invocation Span name to the Lambda function name and changing the Span kind to always be SERVER.

Does This PR Require a Core Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added

[tammy-baylis-swi]

Thanks for fixes and linking the AWS docs in docstring.

[xrmx]

There are cases where span can be of other kinds:

"The span kind for both types of SQS spans SHOULD be CONSUMER"
https://opentelemetry.io/docs/specs/semconv/faas/aws-lambda/#sqs

[herin049]

@xrmx I saw the documentation for SQS events too and I find it a bit ambiguous, but to me it still appears that the parent invocation span type should be SERVER based on the following statement in the spec:

For the SQS event span, if all the messages in the event have the same event source, the name of the span MUST be process. If there are multiple sources in the batch, the name MUST be multiple_sources process. The parent SHOULD be the SERVER span corresponding to the function invocation.

The key phrase being "The parent SHOULD be the SERVER span corresponding to the function invocation."

From what I can tell, both the Java and JavaScript instrumentation libraries always have the initial Span be the SERVER span corresponding to the function invocation, and create additional child Spans for the SQS events.