[chore][receiver/datadogreceiver] migrate feature gates to metadata.yaml

[mangod12]

Description

Migrate the receiver.datadogreceiver.Enable128BitTraceID and receiver.datadogreceiver.EnableMultiTagParsing feature gates to be declared in metadata.yaml and code-generated via mdatagen.

This follows the convention enforced by the forbidigo linter introduced in #47506 and continues the work tracked in #46116, following the same pattern as recent migrations (#48066, #48240, #48281, #48466).

No behavior change for users: the feature gate IDs, stages, descriptions, from_version values, and reference URLs are preserved. The receiver/datadogreceiver forbidigo exclusion is removed from .golangci.yml because the component no longer manually registers feature gates outside generated metadata.

Link to tracking issue

Part of #46116

Testing

From receiver/datadogreceiver:

• go tool -modfile=../../internal/tools/go.mod go.opentelemetry.io/collector/cmd/mdatagen metadata.yaml
• CGO_ENABLED=0 go test ./...
• CGO_ENABLED=0 go tool -modfile=../../internal/tools/go.mod github.com/golangci/golangci-lint/v2/cmd/golangci-lint run --config ../../.golangci.yml ./...

From the repository root:

• goimports -w -local github.com/open-telemetry/opentelemetry-collector-contrib on changed Go files
• gci write -s standard -s default -s "prefix(github.com/open-telemetry/opentelemetry-collector-contrib)" on changed Go files
• git diff --check

Documentation

receiver/datadogreceiver/documentation.md is generated from metadata.yaml and now lists the migrated feature gates.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mangod12 / name: mangod12 (a40592d)

[github-actions]

Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib.

Important reminders:

• Read our Contributing Guidelines.
• Sign the CLA if you haven't already.
• First-time contributors should have at most one PR not marked as draft until their first PR is merged.
• If your change isn't one of our priority components, reviews may take more time.
• Give reviewers at least a few days before pinging them for feedback.
• If you need help or struggle to move your PR forward:
  • Ask questions regarding general setup, development process, or contributor etiquette in #opentelemetry-new-contributors.
  • Raise technical or Collector-specific questions in #otel-collector-dev or a Collector SIG meeting.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Moves Datadog receiver feature-gate registration to mdatagen-driven metadata and updates code/tests to use the generated metadata gate definitions.

Changes:

• Added feature_gates entries to metadata.yaml and generated component documentation.
• Replaced in-code feature gate registration/usage with internal/metadata feature gate variables.
• Adjusted tests to enable/disable the new metadata-defined gates via the global registry.

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
receiver/datadogreceiver/receiver.go	Switches 128-bit TraceID gate check to metadata-generated feature gate
receiver/datadogreceiver/metadata.yaml	Defines Datadog receiver feature gates for code generation
receiver/datadogreceiver/internal/translator/tags.go	Removes local gate registration; uses metadata-generated MultiTagParsing gate
receiver/datadogreceiver/internal/translator/tags_test.go	Updates tests to reference metadata-generated gate IDs
receiver/datadogreceiver/documentation.md	Adds generated docs listing available feature gates
receiver/datadogreceiver/config.go	Removes in-code feature gate registration for 128-bit TraceIDs
.golangci.yml	Removes Datadog receiver-specific forbidigo exclude rule

Files not reviewed (1)

• receiver/datadogreceiver/internal/metadata/generated_feature_gates.go: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mangod12]

This file is generated by mdatagen, and the committed table rows use the standard single leading pipe format. I rechecked the generated file locally; there is no double-leading-pipe row to fix.

[mangod12]

I kept this description text unchanged from the existing manual feature gate registration to avoid changing user-visible feature gate metadata in this migration-only PR.

[mangod12]

I tested removing skip_strict_validation and mdatagen fails because these are legacy IDs with the receiver.datadogreceiver prefix, and EnableMultiTagParsing preserves the existing PR reference URL. This matches the pattern used by recent metadata migrations for legacy gates.

[otelbot]

Thank you for your contribution @mangod12! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey. If you are getting started contributing, you can also join the CNCF Slack channel #opentelemetry-new-contributors to ask for guidance and get help.