Add reentry option for periodic failure of the underlying GKE cluster during config controller creation during bootstrap setup-kcc.sh script - using standard instead of autopilot

Periodically the GKE cluster will fail to come up. Sometimes it will still eventually complete after the 30 min timeout - other times the cluster will be stuck at 64%.

Remember to check that shieldedVM is off from a previous LZ deploy in the org

compute.requreShieldedVMs
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/issues/132

```
root_@cloudshell:~/kcc-kls/20230719/gcp-tools/scripts/bootstrap (kcc-kls-cluster)$ ./setup-kcc.sh -f pdt-kls.env

..
Waiting for operation [projects/kcc-kls-cluster/locations/northamerica-northeast1/operations/operation-1691029053375-601fb6208033c-918c34b7-3db667f0] to complete...failed.
ERROR: (gcloud.anthos.config.controller.create) Operation https://krmapihosting.googleapis.com/v1/projects/kcc-kls-cluster/locations/northamerica-northeast1/operations/operation-1691029053375-601fb6208033c-918c34b7-3db667f0 has not finished in 1800 seconds. The operations may still be underway remotely and may still succeed; use gcloud list and describe commands or https://console.developers.google.com/ to check resource state.
```

Add an option to the script so that we can reuse the project, VPC and firewalls created before KCC creation

see
https://github.com/ssc-spc-ccoe-cei/gcp-tools/blob/main/scripts/bootstrap/setup-kcc.sh#L155

and a doc adjustment to
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/advanced-install.md#gke-autopilot---recommended

and

https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/README.md#gke-standard

workaround - use the -a option (autopilot not standard)

workloads including the config-connector operator will come up