flaky testcontainers tests

[ndr-brt]

Feature Request

Looks like we have some flaky tests, caused by the way we are using testcontainers.
An analysis on the issue has been made in the tractus-x edc context:

every test that involves testcontainers in fact could cause issues, because testcontainers itself spins up a connector with an exposed port, and this happens always after the getFreePort is called, here's the suspect:

301c3c46fe23   testcontainers/ryuk:0.11.0   "/bin/ryuk"              29 seconds ago   Up 28 seconds      0.0.0.0:49158->8080/tcp, :::49158->8080/tcp                           testcontainers-ryuk-5b664308-1f43-4381-962d-ed6531f5c6ef

the port that it uses is generated randomly after the getFreePort is called to define the connector configuration but before the connectors are actually started, like:

• EDC test runtime defines ports to be used by choosing not used ones
• testcontainers spins up a container that could use one of the ports already defined by the EDC test runtime
• EDC test runtime spins up the runtimes, that could break because one of the port has been used by testcontainers

(ref. eclipse-tractusx/tractusx-edc#1027 (comment))

Which Areas Would Be Affected?

end to end tests

Why Is the Feature Desired?

avoid test flakyness

Solution Proposal

• spin testcontainers before defining ports to be used (so make them not statically generated as it is now)
• force the ryuk port to be generated by getFreePort (if that's possible)