[Data] Update whether release tests use autoscaling (#51562)

Some of the release test metrics are difficult to interpret because of
autoscaling. So, this PR updates many of them to use fixed-size
clusters.

See [What sort of cluster should release tests
use?](https://docs.google.com/spreadsheets/d/1JF-KNNOQfQg-oRGJQwX7oPHCrDuDBNyFufTgxDTiKsQ/edit?gid=0#gid=0)

---------

Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>

Author: bveeramani

release/nightly_tests/dataset/all_to_all_compute.yaml renamed to release/nightly_tests/dataset/autoscaling_all_to_all_compute.yaml

@@ -0,0 +1,22 @@
+cloud_id: {{env["ANYSCALE_CLOUD_ID"]}}
+region: us-west-2
+
+advanced_configurations_json:
+    BlockDeviceMappings:
+        - DeviceName: /dev/sda1
+          Ebs:
+            DeleteOnTermination: true
+            VolumeSize: 512
+
+head_node_type:
+    name: head_node
+    instance_type: m5.2xlarge
+    resources:
+      cpu: 0
+
+worker_node_types:
+    - name: worker_node
+      instance_type: m5.4xlarge
+      min_workers: 32
+      max_workers: 32
+      use_spot: false

release/nightly_tests/dataset/fixed_size_all_to_all_compute.yaml

@@ -17,6 +17,6 @@ head_node_type:
 worker_node_types:
     - name: worker-node
       instance_type: m5.2xlarge
-      min_workers: 0
+      min_workers: 10
       max_workers: 10
       use_spot: false