Partition server start/stop in upgrade process

Users would like to be physically present when their servers are being started or stopped to ensure they can fix anything that goes wrong promptly.  However sitting through lengthy data downloads and uploads is not so fun.  This allows them to only be present when servers are starting/stopping.

More context: https://chef.leankit.com/Boards/View/87539983/129913878
CI: http://wilson.ci.opscode.us/job/chef-server-12-trigger-ad_hoc/103/
I put those in just to make the path clear for users.  It seems simpler to have a list of three commands to run in order as opposed to figuring out what our hidden assumptions are around brining up or down a server.  Not that it's complicated, but setup in the upload step has a reconfigure(false) for example.