hybrid orchestration (terraform/kubernetes/gcloud/console) - enablement/procedures/docs around mixed hybrid environments - customer ask

update in the staging wiki https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/DevOps
reference gcloud/k8s scripting https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/gh766-script/solutions/setup.sh#L145

There has requests over the last while and this week on working with other orchestration methods than just the kcc kubernetes cluster.
Resources that are out-of-band from the yaml management of the k8s intent engine
This is also discussed in the issue #817.

How can we support a client that wishes to use the base 5 packages
- core-landing-zone
- client-setup
- client-landing-zone
- client-project-setup
- gatekeeper-policies

but then wishes to create additional infrastructure (like a 2nd client set) in gcloud or terraform

```mermaid
graph LR;
style LZV2 fill:#44f,stroke:#f66,stroke-width:2px,color:#fff,stroke-dasharray: 5 5
%% mapped and documented
project/hub-env-->core-landing-zone;
client-setup;
client-setup-->dns-project;
client-setup-->kcc-management-project;
client-landing-zone-->client-setup;
client-project-setup-->client-landing-zone;
client-project-setup-->client-management-project;
gatekeeper-policies;

kcc-management-project;
core-landing-zone-->kcc-management-project;
dns-project-->core-landing-zone;
logging-project-->core-landing-zone;
client-management-project-->client-setup;
host-project-->client-landing-zone;

```
[mermaid - diagrams as code](https://mermaid-js.github.io/mermaid/#/flowchart?id=graph)