Migrate to aws-xray-sdk-go/v2

[purple4reina]

What does this PR do?

Motivation

Original PR: #190. Opening here so we can run the integration tests.

Testing Guidelines

Additional Notes

Types of changes

• Bug fix
• New feature
• Breaking change
• Misc (docs, refactoring, dependency upgrade, etc.)

Checklist

• This PR's description is comprehensive
• This PR contains breaking changes that are documented in the description
• This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
• This PR impacts documentation, and it has been updated (or a ticket has been logged)
• This PR's changes are covered by the automated tests
• This PR collects user input/sensitive content into Datadog

[purple4reina]

I tested this and can confirm that merging xray traces still works as expected. Created a lambda function which makes an http call to another lambda function, both with xray tracing enabled. I was able to see the xray spans properly merged with the dd spans.

[nhulston]

Do we need to update the aws-xray-sdk-go version in the integration tests? e.g. https://github.com/DataDog/datadog-lambda-go/blob/11287d33321ef7e39820e54d215ea98c45978882/tests/integration_tests/error/go.mod

otherwise LGTM

[purple4reina]

Do we need to update the aws-xray-sdk-go version in the integration tests? e.g. 11287d3/tests/integration_tests/error/go.mod

otherwise LGTM

Interesting. The tests still pass without that update. I think go mod replace must know the right thing to do? Output from the build shows the correct version of xray sdk was used too https://github.com/DataDog/datadog-lambda-go/actions/runs/13710484821/job/38345752829?pr=194#step:8:14. I say let's keep it how it is, if it aint broke don't fix it.