[dotnet] Mark test test_metadata_content_with_process_tags as a missing feature for now

[gleocadie]

Motivation

.NET tracer supports only config v1 protocol but the libdatadog library-config emits v2. This misalignment causes the system-tests to fails in CI.

Changes

Decorate the test test_metadata_content_with_process_tags as bug. The goal being to detect when .NET library support v2 protocol and the test needs to be updated accordingly.

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

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• No system-tests internal is modified. Otherwise, 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 (or removed)?
  • Get a review from R&P team

[github-actions]

CODEOWNERS have been resolved as:

tests/parametric/test_process_discovery.py                              @DataDog/system-tests-core @DataDog/apm-sdk-capabilities