OnBoarding: Host and container guardrail testing

[robertomonteromiguel]

Motivation

The feature "guardrail" has been implemented for some languages.
This PR creates a new scenario to test unsupported version of the language.
In this case we are testing node18 for supported language version and node16 to test a unsupported version of the language

Changes

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

• Relevant label (run-parametric-scenario, run-profiling-scenario...) are presents
• 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

[szegedi]

This will only start working as expected once the guardrails change is released, won't it?

[robertomonteromiguel]

Nop, in the main pipeline the test with node16 are working (using the latest release).