One push deploys

This will make it so the monitor will exit on completion of the deploy that was executed.  It will exit with a non-zero exit status if the deploy failed, otherwise it will exit normally.

It should be noted that this is hooking up a second poller to the monitor (conditionally) that does the exact same API call that is done to populate the data for the monitor.  There might be a clever way that I can share that data, but it was too nested in the spies and such of the monitor lib to try and do so for this feature.  I fully expect that AWS can handle the traffic though.
I am not totally opposed to the idea, but I mostly approached it from a "testing in isolation" perspective (though I didn't test module by itself since that wasn't in place).

To break that explanation down a bit more, if I were to convey the purpose of this method from a high level, it would be something like this:

```
#launch_stack_monitor
  If opitions[:browser] is passed in, open the browser
  If options[:monitor] is passed in, open the monitor and pass in the options
  If neither, do nothing
```

If I go with your suggested change, my above description then has to change to be something like `If options[:monitor] is passed in, open the monitor and pass in the options (also, that track option... make sure to parse that as well`.  Moving it to a new method allows me to test the logic in isolation a bit more.

Both have their flaws, but that is where I am coming from.