Fix parametric instability at container start

[cbeauchesne]

Motivation

On PARAMETRIC scenario, ports conflicts can prevent containers to start.

Changes

• Use lower ports to prevent port collision
• remove any hack that was made to mitigate the issue

Tests

• run 1 : https://github.com/DataDog/system-tests/actions/runs/11662709913/attempts/1
• run 2 : https://github.com/DataDog/system-tests/actions/runs/11662709913/attempts/2 (failure not on parametric)
• run 3 : https://github.com/DataDog/system-tests/actions/runs/11662709913/attempts/3
• run 4 : https://github.com/DataDog/system-tests/actions/runs/11662709913/attempts/4
• run 5 : https://github.com/DataDog/system-tests/actions/runs/11662709913/attempts/5

Then only remove hacks, and redo 5 tests :

• run 6 : https://github.com/DataDog/system-tests/actions/runs/11664343360/attempts/1 (failure not related)
• run 7 : https://github.com/DataDog/system-tests/actions/runs/11664343360/attempts/2 (failure not on parametric)
• run 8 : https://github.com/DataDog/system-tests/actions/runs/11664343360/attempts/3 (failure not on parametric)
• run 9 : https://github.com/DataDog/system-tests/actions/runs/11664343360/attempts/4
• run 10 : https://github.com/DataDog/system-tests/actions/runs/11664343360/attempts/5

It makes 8 * 3 * 10 = 240 consecutive successful runs (1 parametric failure, but not related to port attribution)

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