[CI] Add m5.2xlarge target to more test suites

[amogkam]

Signed-off-by: Amog Kamsetty [email protected]

Follow up to #28736

Add m5.2xlarge target to the remaining test suites that require it.

Why are these changes needed?

Related issue number

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 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 :(

[matthewdeng]

@krfricke @amogkam do we have general guidelines for which tests should use which instances? Is the limiting factor memory or something else?

[jiaodong]

test_batchpredictor_runtime failed due to failing 15secs time check

[amogkam]

@matthewdeng All tests should probably be able to use smaller instances, but would require some rewriting.