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

[e-n-0]

It's been some times since we discussed about this.
From what I remember, we divided our tasks:

• ✅ @e-n-0: Duplicate all my tests classes to use base class and pass all the tests that I want to skip with an @irrelevent tag
• ✅ @e-n-0: Use separate scenario (inside the external-processing group) for special case where a rule set is defined
• @cbeauchesne: Make changes in the system-test core to allow the imports of the tests (tests currently failing because there have multiple scenarios linked to them due to the import)
• @e-n-0 & @cbeauchesne: See how we could report the results to the Feature Parity Dashboard

[cbeauchesne]

@e-n-0 I've fixed the common-test-code case.

Ping me if you need any help to move forward.

[cbeauchesne]

Two mall details, then all good