Update aws sdk2 instrumentation to follow semconv

[laurit]

Resolves #14580
Update attribute names and types and enable the ones that are in spec without the experimental falg. This PR also affects some attributes that were generated without the experimental flag, but aren't in the semantic conventions such as aws.queue.url and aws.queue.name.

[jaydeluca]

should we mark this as a breaking change? With some description like:

The following attributes have been renamed to adhere to semantic conventions:

• aws.dynamodb.provisioned_throughput.read_capacity_units -> aws.dynamodb.provisioned_read_capacity (value went from long to double)
• aws.dynamodb.provisioned_throughput.write_capacity_units -> aws.dynamodb.provisioned_write_capacity (value went from long to double)
• aws.dynamodb.exclusive_start_table_name -> aws.dynamodb.exclusive_start_table

And the following attributes are no longer emitted by default, but can be enabled with the experimental flag:

• aws.queue.name
• aws.lambda.function.name
• aws.lambda.function.arn

[laurit]

should we mark this as a breaking change?

I think so. Our convention is to not emit non-spec attributes by default. By that logic these attributes should have been behind the experimental flag, but apparently we messed up. In

opentelemetry-java-instrumentation/instrumentation/aws-sdk/aws-sdk-2.2/library/src/main/java/io/opentelemetry/instrumentation/awssdk/v2_2/internal/TracingExecutionInterceptor.java

Lines 404 to 409 in e12631d

	if (captureExperimentalSpanAttributes) {
	AwsSdkRequest sdkRequest = executionAttributes.getAttribute(AWS_SDK_REQUEST_ATTRIBUTE);
	if (sdkRequest != null) {
	fieldMapper.mapToAttributes(response, sdkRequest, span);
	}
	}

we check whether experimental flags are enabled but in

opentelemetry-java-instrumentation/instrumentation/aws-sdk/aws-sdk-2.2/library/src/main/java/io/opentelemetry/instrumentation/awssdk/v2_2/internal/TracingExecutionInterceptor.java

Lines 216 to 219 in e12631d

	if (awsSdkRequest != null) {
	executionAttributes.putAttribute(AWS_SDK_REQUEST_ATTRIBUTE, awsSdkRequest);
	fieldMapper.mapToAttributes(request, awsSdkRequest, span);
	}

we don't. So all request attributes are added by default, but response attributes require the experimental flag.

[github-actions]

⚠️ Breaking Change Documentation Required

This PR has been labeled as a breaking change. Please ensure you provide the following information:

Migration Notes Required

Please add detailed migration notes to help users understand:

• What is changing and why
• How to update their code/configuration
• Any alternative approaches if applicable
• Code examples showing before/after usage

Checklist

• Migration notes added to the PR description
• Breaking change is documented in the changelog entry for the next release
• Consider if this change requires a major version bump

Your migration notes will be included in the release notes to help users upgrade smoothly. The more detailed and helpful they are, the better the user experience will be.

---

This comment was automatically generated because the breaking change label was applied to this PR.