AWS: Add the ability to configure throughput on GP3 volumes

GP3 volumes have the ability to configure throughput from 125 MiB/s to
1000 MiB/s. This allows the ability to set this at install time in the
install-config.

https://issues.redhat.com/browse/CORS-4212

Author: jhixson74

machine/v1beta1/types_awsprovider.go

@@ -167,6 +167,13 @@ type EBSBlockDeviceSpec struct {
 	// it is not used in requests to create gp2, st1, sc1, or standard volumes.
 	// +optional
 	Iops *int64 `json:"iops,omitempty"`
+	// The throughput to provision for a volume, with a maximum of 1,000 MiB/s.
+	//
+	// This parameter is valid only for gp3 volumes.
+	//
+	// Valid Range: Minimum value of 125. Maximum value of 1000.
+	// +optional
+	Throughput *int64 `json:"throughput,omitempty"`
 	// The size of the volume, in GiB.
 	//
 	// Constraints: 1-16384 for General Purpose SSD (gp2), 4-16384 for Provisioned

machine/v1beta1/zz_generated.deepcopy.go

@@ -22664,6 +22664,11 @@
           "default": {},
           "$ref": "#/definitions/com.github.openshift.api.machine.v1beta1.AWSResourceReference"
         },
+        "throughput": {
+          "description": "The throughput to provision for a volume, with a maximum of 1,000 MiB/s.\n\nThis parameter is valid only for gp3 volumes.\n\nValid Range: Minimum value of 125. Maximum value of 1000.",
+          "type": "integer",
+          "format": "int64"
+        },
         "volumeSize": {
           "description": "The size of the volume, in GiB.\n\nConstraints: 1-16384 for General Purpose SSD (gp2), 4-16384 for Provisioned IOPS SSD (io1), 500-16384 for Throughput Optimized HDD (st1), 500-16384 for Cold HDD (sc1), and 1-1024 for Magnetic (standard) volumes. If you specify a snapshot, the volume size must be equal to or larger than the snapshot size.\n\nDefault: If you're creating the volume from a snapshot and don't specify a volume size, the default is the snapshot size.",
           "type": "integer",