Add implementation and contract tests for new AWS resources

[ezhang6811]

Description of changes:
Support instrumentation for the following attributes. See this Python PR for the source of feature parity.

• For SNS, extract TopicArn from request body and add to span as aws.sns.topic.arn.
• For Secrets Manager, extract either SecretId from request body or ARN from response body and add to span as aws.secretsmanager.secret.arn.
• For Step Functions, extract activityArn or stateMachineArn from request body, and add to span as aws.stepfunctions.activity.arn or aws.stepfunctions.state_machine.arn respectively.
• For Lambda, extract UUID from request body for event source mapping functions, and add to span as aws.lambda.resource_mapping.id.

In addition, the new resource attribute aws.remote.resource.cfn.primary.identifier is also added for each new resource.

E2E tests show that the new attributes and their associated CFN primary identifiers have been correctly populated for each service.

SNS:

Secrets Manager:

Step Functions:

Lambda:

Contract tests verify the expected span attribute values with example function calls that involve each resource. https://github.com/aws-observability/aws-otel-dotnet-instrumentation/actions/runs/12127063253/job/33813330563?pr=143

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

[vastin]

Both this PR and PR #142 add aws.remote.resource.cfn.primary.identifier. Is there any dependency between them? Should PR #142 be merged firstly?

[ezhang6811]

Both this PR and PR #142 add aws.remote.resource.cfn.primary.identifier. Is there any dependency between them? Should PR #142 be merged firstly?

Yes, #142 should be merged first as it originally implements aws.remote.resource.cfn.primary.identifier, and this PR was rebased on #142 so that this CFN Identifier attribute could be applied for the new resources.