3-networks-hub-and-spoke hardcoded regions us-west1/us-central1 - parameterize them for regionalization security compliance

[fmichaelobrien]

During the 3 section deploy on a clean org ran into hardcoded regions - this will need to be parameterized and fixed to default to northamerica-northeast1 and 2 for security compliance specific to regionalization
see
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/main/3-networks-hub-and-spoke/envs/shared/main.tf#L22

locals {
  env                = "common"
  environment_code   = "c"
  bgp_asn_number     = var.enable_partner_interconnect ? "16550" : "64514"
  dns_bgp_asn_number = var.enable_partner_interconnect ? "16550" : var.bgp_asn_dns
  default_region1    = "us-west1"
  default_region2    = "us-central1"

verify also the other 3-networks-dual-svpc
https://github.com/terraform-google-modules/terraform-example-foundation/blob/master/3-networks-dual-svpc/envs/shared/remote.tf#L21

see
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/main/3-networks-dual-svpc/envs/shared/remote.tf#L21

duplicate of terraform-google-modules/terraform-example-foundation#1172

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days