python/ray/autoscaler/gcp/*.yaml: change scheduling from dict to list

[guoqiao]

Why are these changes needed?

Related issue number

Closes #46248

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • [] Unit tests
  • [] Release tests
  • This PR is not tested :(

[jjyao]

Question, what's the behavior of the existing yaml if scheduling is list instead of dict?

[guoqiao]

Question, what's the behavior of the existing yaml if scheduling is list instead of dict?

@jjyao

Had a try with preemptible: true for ray 2.10.0 (the version we are using).

the result is same and correct for both list and object: vm showing Preemptiblity On in GCP.

Looks like there is a coincidence or workaround to make it work correctly, and that's why the issue is not discovered for so long.

I didn't get the time to try other fields and multi fields cases though.