(QENG-842) Always wait for puppetmaster to be ready when bouncing

Previously, we would only wait for the puppetmaster to be started if a
host config file explicitly requested it. Our init scripts actually
require this waiting pretty much across the board now, so trying to
only do this when it's needed is silly. And even when it's not needed
we only curl once - it's not a ton of overhead.
@colinPL If you stop the service, you should expect to see exit code `7` from `curl` since the service will no longer be listening on that port. Once the service is listening at the specified port you should wait for exit code `0` or `52` (either of these will signify that curl was at least able to initiate a TCP connection to a service listening on the port) when using `http` and exit codes `35` or `60` when using `https` as Brandon has changed this method to do.

It might be a good idea to do `curl_with_retries` after running `stop` to listen for exit code `7` then `curl_with_retries` after running start to listen for one of the exit codes that will signify the port is opening and the application listening on it. This would prevent problems due to slow shutdown time--in some of the jvm projects our init scripts will wait up to 10 seconds after issuing SIGTERM before issuing SIGKILL when running the `stop` command. During this time the service may still be listening at the specified port when the first `curl` command runs and then stop after `curl_with_retries` appears to have verified successful restart.