Add tests for Service Extension (Envoy External Processing)

[e-n-0]

Motivation

Tests the new ASM Integration Service Extension.

Changes

Import tests from APM and ASM that applies to the Service Extension.
The import is using class generation to correctly import tests that should work and skip the ones that will not work.

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

[cbeauchesne]

With that, it'll duplicate base test class. Let meet with zoom to see the best way to achieve this.

[cbeauchesne]

from tests import test_semantic_conventions as base_semantic_conventions


@scenarios.external_processing
class Test_Meta(base_semantic_conventions.Test_Meta):
    @irrelevant(True, reason="The meta component tag would always be http.request and not external-processing")
    def test_meta_component_tag(self):
         super().test_meta_component_tag()
    
@scenarios.external_processing 
class Test_EnvVar(base_semantic_conventions.Test_Meta):
    pass