Add AssuredWorkload support to the folder module (#2390)

* Feat: Add AssuredWorkload support to the folder module

* Formatting

* Use square brackets to access list items

* Docs gen after adding an example to the readme

* Reorder variables

* Formatting

* Reordering outputs, formatting

* Remove try where not needed. Add IAM into the AW example and tests

* Fix tests

* Enable Assured Workloads in E2E tests

* Add compliance_regime and partner enum fields validation

* Rewording validation message for compliance_regime, partner fields

* Sort the list of allowed values alphabetically

* Make the organization dependant on testing environment

* fix tests

* Disable E2E for Assured Workflow example.

This example requires Access Transparency enabled on org level, even
chosing different regime, we need to have `parent` and `organization`
within the same hierarchy, which is not currently the case and requires
more rework of the test framework.

---------

Co-authored-by: Wiktor Niesiobędzki <wiktorn@google.com>

modules/folder/outputs.tf

@@ -14,6 +14,11 @@
  * limitations under the License.
  */
 
+output "assured_workload" {
+  description = "Assured Workloads workload resource."
+  value       = try(google_assured_workloads_workload.folder[0], null)
+}
+
 output "folder" {
   description = "Folder resource."
   value       = try(google_folder.folder[0], null)
@@ -32,7 +37,11 @@ output "id" {
 
 output "name" {
   description = "Folder name."
-  value       = try(google_folder.folder[0].display_name, null)
+  value = (
+    var.assured_workload_config == null
+    ? try(google_folder.folder[0].display_name, null)
+    : try(google_assured_workloads_workload.folder[0].resource_settings[0].display_name, null)
+  )
 }
 
 output "sink_writer_identities" {