Rasp command injection tests

[NachoEchevarria]

Motivation

This PR implements the system tests that will be required for the command injection vulnerability in RASP.

The details of this vulnerability can be found here: https://docs.google.com/document/d/1DDWy3frMXDTAbk-BfnZ1FdRwuPx6Pl7AWyR4zjqRFZw/edit?tab=t.0#heading=h.giijrtyn1fdx

The tests are based on other vulnerabilities tests and have passed under .Net (version not yet merged)

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

• 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

[uurien]

if we are going to have multiple libddwaf min versions, it will worth to move the test to each test file, like we are doing with Rules_Version

[NachoEchevarria]

Good point. I have updated the code addressing your comment.

[robertomonteromiguel]

There are CI failures related with this PR