TOC: Fully parameterize the region across the code - to handle a mix or only nane1 or nane2

By design because of the historical preference to nane1 - some of the config is hardcoded to region 1.
an example is in
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/pull/781
in
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/solutions/experimentation/core-landing-zone/lz-folder/audits/logging-project/cloud-storage-buckets.yaml#L30

```
spec:
# enable autoclass
# https://cloud.google.com/storage/docs/autoclass
autoclass:
enabled: true
location: northamerica-northeast1
```

There are times when these remaining region settings must be aligned with nane2 including a recent client request.

Push changes in phases by package and CI/CD test each package PR - starting with core-landing-zone