Enabling Already Consistent .NET Tests

[link04]

Motivation

APMAPI-602 where I am in charge of confirming that the expected .NET tests are matching the telemetry expectations and related config system test expectations.

Changes

Updated the .NET parametric service so that we don't set an empty service name and let the tracer pick up the config one when the one used for custom spans is an empty string.

Enabled in the related manifest files the classes where I ran the tests manually and had success passing the tests.

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, 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
• CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
• 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