[receiver/datadog] Make gRPC, HTTP, and AWS-SDK spans compliant with the OTel Semconv

[cyrille-leclerc]

Description

• gRPC: Make client & server gRPC spans compliant with the OTel Semconv
• HTTP: Make http.request and web.request span names compliant with OTel semconv
• Database: Compliance improvements on database client call spans received via the Datadog receiver:
  • The db.instance tag is now mapped to the OTel attribute db.namespace instead of db.collection.name.
  • The db.sql.table tag is mapped to the OTel attribute db.collection.name.
  • The db.statement tag is mapped to the OTel attribute db.query.text.
• AWS SDK: Improve the compliance with OTel Semantic Conventions for AWS SDK spans in the Datadog receiver.
  • Set span name according to AWS SDK conventions.
  • Set rpc.system, rpc.method and rpc.service attributes.
• Bump OTel Semantic Conventions from v1.30.0 to v1.37.0 in the Datadog receiver.
  • The Datadog tag runtime is now mapped to the OTel attribute container.runtime.name instead of container.runtime.

Link to tracking issue

Fixes:

• [receiver/datadog] dd-trace-go HTTP and Web spans names don't comply with OTel Semconv #44722
• [receiver/datadog] RPC spans name and attributes don't comply with OTel Semconv #44671
• [receiver/datadog] AWS SDK spans name and attributes don't comply with OTel Semconv #44723

Testing

End to end test with dd-trace-java

gRPC span

HTTP request span

Documentation

[dehaansa]

One question, and needs a changelog, otherwise LGTM

[xiu]

(nit) this seems to be missing a word

[cyrille-leclerc]

fixed

[cyrille-leclerc]

As seen with @xiu , does work with RPC spans produced by dd-trace-java that use slightly different span tags

[cyrille-leclerc]

Build failing due to flaky tests that are not related to this PR

FAIL	github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sattributesprocessor	410.594s

[iblancasa]

You are adding changelogs from other PRs or something.

[cyrille-leclerc]

This PR contains several distinct but related improvements so I created multiple change log files.

[dehaansa]

LGTM. I don't have a strong opinion on multiple changelogs from one PR, I don't see anything in the contributing.md that explicitly states only one per PR, seems like added clarity is always good.