Default assumption should be PAS/PKS co-located on same opsmgr

[aegershman]

Hey there!

Since it appears all the terraforming-<iaas> repos are being deprecated in favor of paving-pas/paving-pks I wanted to throw in my 2-cents on this before things got too far down the "separated environments" path:

Unless it's recommended that PAS and PKS foundations be separate (e.g., two separate opsmgrs with entirely separate CIDRs, etc), I feel it should be assumed that PAS and PKS tiles and environments will be, or could be, co-located on the same opsmgr.

The reason I say this is because it seems terraforming-PAS and terraforming-PKS are treated as if they'd be entirely separate deployments rather than co-located in the same VPC / CIDR block subdivisions for subnets / shared opsmgr / shared BOSH director, etc., so it'd be nice if a co-deployed environment of PAS/PKS as one foundation were treated as a single deployment topology rather than as two separate deployments.

Put another way, I feel default assumption should be to have PAS and PKS as one deployment, and optionally be able to deploy only PAS or only PKS, rather than the default assumption being that they're deployed separately & requiring reconfiguration of the terraform in order to get PAS and PKS colocated.

Thanks for the consideration 👍