Unstable UpgradeWithNewInvocation test

[tillrohrmann]

I've encountered an instance of the UpgradeWithNewInvocation test failing: https://github.com/restatedev/restate/actions/runs/11970222544/job/33373161856. It looks as if the service v2 container is not yet running when the test tries to register it here:

sdk-test-suite/src/main/kotlin/dev/restate/sdktesting/tests/UpgradeWithNewInvocation.kt

Line 69 in fb737ce

registerService2(metaURL)

.

Would it be possible to wait until all service containers are up and running before starting the test? Alternatively, adding a longer retry policy for the registration could harden this call.