Updating Config Consistency Telemetry Test

[link04]

Motivation

Noticed something not matching as expected when trying to run the test locally for .NET to test that DD_SERVICE was returned as expected.

Changes

Instead of using existing data and helper methods, updated the test to look directly for the env var by name as expected in the telemetry based on the new consistency efforts, i.e. DD_TRACE_HTTP_SERVER_ERROR_STATUSES instead of DD_HTTP_SERVER_ERROR_STATUSES which we should change in both Env Var customers can use and returned config name in the respective SDK language config norm file before being able to completely pass the test.

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

[mtoffl01]

Is case sensitivity an issue here? E,g, User-Agent vs user-agent?

[link04]

Nah it shouldn't be based on the RFC, I just tried pulling the same values for the configs that is recommended for the others tests in the RFC(swap some around to change them from the defaults):
https://docs.google.com/document/d/1kI-gTAKghfcwI7YzKhqRv2ExUstcHqADIWA4-TZ387o/edit#heading=h.e0s28phvgd5g

[khanayan123]

Thank-you for these changes!