Make setup-kcc.sh -p the default - to enable the GKE cluster public endpoint

see -p flag introduced to switch from default public to default private
https://github.com/ssc-spc-ccoe-cei/gcp-tools/pull/53

shadow https://github.com/ssc-spc-ccoe-cei/gcp-tools/issues/48

Following triage of
#534
and
#539
something off with my clean KCC env obrien.industries (will check the diffs on setup-kcc.sh) - as my older 6 week kcc.landing.systems - even with the admission errors will edit the yaml no problem
```
root_@cloudshell:~ (kcc-kls-cluster3)$ kubectl edit validatingwebhookconfiguration/gatekeeper-validating-webhook-configuration
Edit cancelled, no changes made.
root_@cloudshell:~ (kcc-kls-cluster3)$
```

Triaging connection
older server working has 35 address in .kube/config
```
server: https://35.203.120.71
name: gke_kcc-kls-cluster3_northamerica-northeast1_krmapihost-kcc-kls3
```

newer server has private address
```
server: https://172.16.0.130
name: gke_kcc-oi-cluster_northamerica-northeast1_krmapihost-kcc-oi
```

Found above issue - forgot to add -p for public endpoint

ran./setup-kcc.sh -af kcc.env

for

https://github.com/ssc-spc-ccoe-cei/gcp-tools/commit/941d542e5024144b541136e19700b50cd8eaf895