bug: pulumi remote command fails on first up

[TylerHillery]

Issue Description

On the first pulumi up, pulumi is going to fail because it's going to try to remote command into the droplet before it's provisioned.

I could add an specific resource dependency for the remote image but it's going to be tough to configure because the remote command relies on the cloud init script to be finished before running. Even if I use the ssh key instead of Tailscale to be installed I have to wait for other services to be installed like Docker etc.

I am sure I could modify the remote command to add a "health check" of some sorts until it's okay to precede. I am not sure it's worth the effort right given the fact the cloud init script takes care of starting the services on initial up I don't need the remote command to be executed.

Something to solve for a later date.