[Data] Fixed max_retries for hash shuffle

[alexeykudinkin]

Why are these changes needed?

Cherry-pick of #57572

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 pre-commit jobs to lint the changes in this PR. (pre-commit setup)
• 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 :(

[gemini-code-assist]

Code Review

This pull request aims to improve the robustness of the hash shuffle operation by enabling indefinite retries for its constituent tasks. The changes correctly apply max_retries=-1 for the shuffle map tasks and max_task_retries=-1 for the aggregator actor tasks, which is a solid approach. However, I've identified one high-severity issue where a fixed timeout on a ray.get() call could undermine the benefit of indefinite retries. Please see my detailed comment below.