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/
Sound make these explicit in the help (this is step 1, etc.), the current ordering that shows up is confusing, and even if it was the correct order, that would only be implicit.