fix: Fix duplicate and out-of-order key in supported_configurations

[jboolean]

What does this PR do?

Fixes main​ by fixing duplicate and disordered keys in env var files.

Motivation

This was causing failures on my other branch not attributable to my changes #4100 and causing confusion

Reviewer's Checklist

• Changed code has unit tests for its functionality at or near 100% coverage.
• System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
• There is a benchmark for any new code, or changes to existing code.
• If this interacts with the agent in a new way, a system test has been added.
• New code is free of linting errors. You can check this by running ./scripts/lint.sh locally.
• Add an appropriate team label so this PR gets put in the right place for the release notes.
• Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild.

Unsure? Have a question? Request a review!

[jboolean]

• fix: Fix duplicate and out-of-order key in supported_configurations #4121 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-11-13 16:42:58

Comparing candidate commit b333831 in PR branch jb/fix-duplicate-key-in-supported_configurations with baseline commit bce309f in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 23 metrics, 1 unstable metrics.

[datadog-official]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: b333831 | Docs | Datadog PR Page | Was this helpful? Give us feedback!}

[jboolean]

The generation script moves this key to be in lexicographical order.

This change was made by running go run ./scripts/configinverter/main.go generate

[jboolean]

This duplicate key, which also appears on 615, is removed by running make test.

[jboolean]

/merge

[dd-devflow-routing-codex]

View all feedbacks in Devflow UI.

2025-11-13 17:07:24 UTC ℹ️ Start processing command /merge

---

2025-11-13 17:07:35 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2025-11-13 17:52:36 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 18m (p90).

---

2025-11-13 18:07:28 UTC ❌ MergeQueue: The checks failed on this merge request

Tests failed on this commit fbebbbc:

• unit-integration-tests / test-core

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

[jboolean]

test_core is failing 3/4 times. Unrelated

/merge

[jboolean]

/merge

[dd-devflow-routing-codex]

View all feedbacks in Devflow UI.

2025-11-13 18:09:39 UTC ℹ️ Start processing command /merge

---

2025-11-13 18:09:44 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 18m (p90).

---

2025-11-13 18:22:38 UTC ℹ️ MergeQueue: This merge request was merged

[jboolean]

Merge activity

• Nov 13, 6:14 PM UTC: Graphite couldn't merge this PR because it failed for an unknown reason (GitHub is reporting that this PR is not mergeable, despite passing required status checks defined by your branch protection rules. Please check your rulesets for additional blocking criteria. Graphite Merge Queue does not currently support rulesets. Please contact Graphite support for further assistance.).