[Bug]: dstack apply detaches from runs with "Can't connect to the remote host"

[r4victor]

Steps to reproduce

dstack marks a run as running if at least one job is running. If the first job is still pulling but some other job is already running, dstack apply tries to connect to the first job and exits with "Can't connect to the remote host" after some timeout.

1. Create a two node fleet.
2. Start a multi-node task. Use a heavy docker image that is pulled on the second instance but not on the first.
3. Get the error:

Submit a new run? [y/n]: y
little-turtle-1 provisioning completed (running)
Can't connect to the remote host

dstack apply should connect to the first job only when it's running.

Actual behaviour

No response

Expected behaviour

No response

dstack version

master

Server logs

No response

Additional information

No response