fix(scheduler): initially wait for container to start

This should fix up the issue where users are waiting up to 20 minutes for the scheduler to notify them that their application failed to deploy.

closes #1422 
closes #1534 
closes #1539 

I was trying to think of a fail condition that's not 'failed' but would indicate a dead service, but I couldn't think of one.