Package an AMI to support amazon

  + The diego-edge-bootstrap upstart task now determines if
    it is running on AWS, and if so, it queries  amazon for the ip in order to set the system domain.
    For AWS, we use <IP>.xip.io for the system domain instead of public dns because we need subdomains to work.
    If we are not running on AWS, we assume that we are running in vagrant and use 192.168.11.11.xip.io

    diego-edge-boostrap writes substitutes the system domain into traffic controller's config file.
    It also saves system domain to /var/diego/system-domain, which the receptor upstart script reads.

Signed-off-by: David Julia <djulia@pivotal.io>
calculate the lrphost dynamically to support aws

Signed-off-by: David Wadden <dwadden@pivotal.io>
reorganized install order and upstart to support aws

Signed-off-by: Matthew McNew <mmcnew@pivotal.io>
add support for vmware fusion in the vagrant file

Signed-off-by: Chelsea Troy <ctroy@pivotal.io>
update how loggregator is compiled

loggregator is no longer in diego release

Signed-off-by: Matthew McNew <mmcnew@pivotal.io>
use all IP addresses to lrpHost

Signed-off-by: Chelsea Troy <ctroy@pivotal.io>
ensure all loggregator submodules are updated on gocd

Signed-off-by: Matthew McNew <mmcnew@pivotal.io>
remove keys

Signed-off-by: Matthew McNew <mmcnew@pivotal.io>
Bump Version: 8 -> 9