split out of cf for deployment

* define diego1/diego2 networks for our own deployment
* introduce a template for pulling in external services (nats, etcd, cc, loggregator)
* generate_deployment_manifest still depends on cf-release but only uses its
  infrastructure template, which declares its networks and static IPs, etc.
* the cc srv_api_uri is duplicated, which is risky, but the problem goes away
  once we have proper service discovery

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>