Fix retry rate on parallel test runs - pt. I

What does this MR do and why?

After merging Add ability to run e2e tests in parallel within a single CI job, the goal before activating the parallelization is to bring down the retry rate that occurs when there are collisions of operations in parallel execution. There are few things needed and this MR is an iteration to help breakdown the changes:

• Make the runner creation unique instead of relying on the Time which creates collisions when runners are created at the same time
• Allocate dynamic ports to avoid collisions when services run on the same port at the same time

This represents the rate (at half the cores available) before these changes:

After the changes:

This will still be merged with the parallelization enabled until we get as close as possible to 4 (master retry rate)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.