warmup and backup enhancements, now rest endpoint

[ipapapa]

This PR does two things:
(a) enhances the warm up process by

• delaying the start of Dynomite. We do not need to start Dynomite before the warm up finishes. The reason is that replicated data are received by peer nodes even though the node is out of Discovery. That may increase the memory footprint of Dynomite.
• asking the local rack for the nodes with the same token

(b) adds a REST endpoint in Florida in which information about the status of the node (and the processes running) in JSON format. The reason, we added this feature is: to have a single point of ground truth about the node without having to parse logs (especially useful for S3 backups). It will allow us to check before we move on.
For now, the following are supported:

• warmup (status: not started, completed, pending, unsuccessful)
• backup (status: not started, completed, pending, unsuccessful)
• restore (status: not started, completed, pending, unsuccessful)
• dynomiteAlive
• storageAlive
• healthy

(c) restructured backups and restores so that we can extend them to other platforms as well. The main benefit from that would be OSS folks who use Dynomite-manager with Google Cloud etc.

[ipapapa]

JSON would like the following image:

The new Status REST endpoint integrates very well with Spinnaker as well.