feat: Use block storage for Crunchy Postgres and RabbitMQ for AWS (PSKD-1282)

[dhoucgitter]

Changes

• For AWS, create block storage classes for RabbitMQ and Crunchy Postgres use so that persistent volume claim requests in those applications create elastic block storage based persistent volumes instead of using NFS based persistent volumes for those applications.
• For AWS, configure the two new io2 based storage classes with reasonable iopsPerGB and Throughput defaults based on volume sizes for satisfactory RabbitMQ and Crunchy Postgres performance. Allow for configuration variable overrides to choose different volume types or performance related parameters for the new storage classes if needed.

Development tests

Scenario	Provider	DAC deploy method	K8s version	Cadence	RabbitMQ PVs	RabbitMQ PV IOPS	Crunchy Postgres PVs	Crunchy Postgres PV IOPS	Provisioner	Notes
1	AWS	deploy cmd	1.30.9	stable 2025.01	three 4Gi RWO io2-vol-mq based PVs	three 4Gi PVs at 2000 IOPS	four RWO io2-vol-pg based PVs, each 128 Gi PV	5120 IOPS	ebs csi driver	Successful Viya deployment, all pods including the RabbitMQ and Crunchy pods using block storage PVs are at Running
2	Azure	deploy cmd	1.30.9	stable 2025.01	three 2Gi RWO sas storage class based PVs	n/a	four RWO sas storage class based PVs	n/a	nfs-subdir-external-provisioner	For Azure, verified that existing nfs-based pg-storage and sas storage classes were created as needed, four 128Gi Crunchy persistent volumes were provisioned by the nfs-subdir-external-provisioner as expected, three 2Gi RabbitMQ persistent volumes were provisioned by the nfs-subdir-external-provisioner as expected, RabbitMQ and Crunchy pods are healthy and Running, stable:2025.01 Viya deployment was successful, all pods have reached Running and are stable
3	GCP	deploy cmd	*	*	three 2Gi RWO sas storage class based PVs	n/a	four RWO sas storage class based PVs	n/a	nfs-subdir-external-provisioner	For GCP, verified existing nfs-based pg-storage and sas storage classes were created as needed, four 128Gi Crunchy persistent volumes were provisioned by the nfs-subdir-external-provisioner as expected, three 2Gi RabbitMQ persistent volumes were provisioned by the nfs-subdir-external-provisioner as expected, RabbitMQ and Crunchy pods are Running, Viya deployment was successful

[saschjmil]

Looks good!

[joboon]

Looks good to me, just a question for my own understanding.