CCP 2.0 includes the following changes:

1) CCP migration from AWS to GOOGLE.

CCP jobs (except for jobs need connection to ddboost and netbackup) now
no longer need external workers, therefore ccp tags for external workers
are removed.

The tfstate backend for AWS and GOOGLE are stored seperatedly on s3
bucket, `clusters-aws/` for aws and `clusters-google/` for google,
set_failed are also different between the two cloud providers.

2) Separate gpinitsystem from the gen_cluster task

When failures occur in production for gpinitsystem itself, it is
important for a developer to be able to quickly distinguish whether it
is a CCP failure, or a problem with the binaries used to init the GPDB
cluster. By separating the tasks, it is easier to see when gpinit itself
has failed.

3) The path to scripts used in CCP has changed

Instead of all of the generic scripts being in `ccp_src/aws/` they are
now in a better location of `ccp_src/scripts/`.

4) Paramater names have changed

platform is now PLATFORM for all references in CCP jobs

5) NVME jobs

Jobs that used NVME in AWS have been migrated to an identical feature
for NVME in GCP but this does include a change to the terraform path
specified in the job.

6) Instance types mapping from Ec2 to GCE

The new paramater name for specifying instance type in GCP jobs is
`instance_type`. There is not always a 1:1 match for instance types so
there are slight differences in available resources for some jobs.
Signed-off-by: NKris Macoskey <kmacoskey@pivotal.io>