Set repo_overrides for @DataDog/profiling

[cbeauchesne]

Motivation

Changes

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• Anything but tests/ or manifests/ is modified ? I have the approval from R&P team
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added, removed or renamed?
  • Get a review from R&P team

[github-actions]

CODEOWNERS have been resolved as:

utils/_features.py                                                      @DataDog/system-tests-core

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3a45853d2a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Include the Nginx profiling owner override

The PROFILING scenario is part of the tracer_release workflow, and manifests/cpp_nginx.yml only disables the process-tags checks, so Test_Profile::test_library and test_agent still run for cpp_nginx. In an nginx-datadog CI run, _get_ci_repo_name() resolves to nginx-datadog; because this new override map omits that repo, those profiling failures continue to be assigned to the default @DataDog/profiling instead of the C++ owner used by the other per-repo maps.

Useful? React with 👍 / 👎.