Automation: deletion of the landing zone should include the 5 ns - policies, logging, networking, projects, hierarchy - or let the config controller handle deletion via kpt live destroy

part of #446

https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/DevOps#delete-the-landing-zone

- 20231130 - restest with the required order - config-control (with permissions last) - re: comment from Alain in https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/pull/740
```
kubectl delete gcp -n projects --all
kubectl delete gcp -n networking --all
kubectl delete gcp -n hierarchy --all
kubectl delete gcp -n policies --all
kubectl delete gcp -n logging --all

# retest and adjust order above and add
kubectl delete gcp -n config-control --all
```

See original documentation
- see https://cloud.google.com/architecture/managing-cloud-infrastructure-using-kpt#delete_the_resources
- see https://cloud.google.com/config-connector/docs/how-to/managing-deleting-resources
- see https://cloud.google.com/anthos-config-management/docs/tutorials/manage-resources-config-controller#delete_the_individual_resources

Add to the documentation and automation, currently we do only
```
kubectl delete gcp --all
```
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/README.md#clean-up
#446
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/gh446-hub/solutions/setup.sh

Why are we not letting the config controller handle services deletion it currently controls - using

```
kpt live destroy $REL_SUB_PACKAGE
```

We will add

```
kubectl delete gcp -n projects --all
kubectl delete gcp -n networking --all
kubectl delete gcp -n hierarchy --all
kubectl delete gcp -n policies --all
kubectl delete gcp -n logging --all
```