test: improve runctl-clusterctl robustness
test: improve runctl-clusterctl robustness

Tests had no labels, making it very difficult to see which one was
failing.

Some tests, such as wanting to see an increased count after a fork, were
inherently racy, whether the status request comes before the controller
kills the extra unwanted worker is a matter of timing. Also, a test that
waited for the first of two workers to be replaced, and then asserted
that both workers were already replaced was racy.

I could get intermittent failures before these changes, but tests seem
much more robust now.

shelbys/strong-supervisor