During the Regional Controls Public Preview, the ComplianceRegime enum value has changed from FREE_REGIONS to REGIONAL_CONTROLS

## Announcement During the Regional Controls Public Preview, the [ComplianceRegime](https://cloud.google.com/assured-workloads/docs/reference/rest/Shared.Types/ComplianceRegime) enum value has changed from `FREE_REGIONS` to `REGIONAL_CONTROLS`. When using the REST API, Terraform, or `gcloud`, ensure that you use the new `REGIONAL_CONTROLS` value. This change does not impact existing Assured Workloads folders that were created using the old value. However, areas with potential impact include the following: * Using the REST API and `gcloud`: * Use `REGIONAL_CONTROLS` instead of `FREE_REGIONS` when calling [organizations.locations.workloads.create](https://cloud.google.com/assured-workloads/docs/reference/rest/v1/organizations.locations.workloads/create) to create a new Assured Workloads folder/workload * Expect `REGIONAL_CONTROLS` as the return value for [ComplianceRegime](https://cloud.google.com/assured-workloads/docs/reference/rest/Shared.Types/ComplianceRegime) from calls to [organizations.locations.workloads.get](https://cloud.google.com/assured-workloads/docs/reference/rest/v1/organizations.locations.workloads/get) and [organizations.locations.workloads.list](https://cloud.google.com/assured-workloads/docs/reference/rest/v1/organizations.locations.workloads/list) * Using Terraform: * Use `REGIONAL_CONTROLS` instead of `FREE_REGIONS`