[Data] Remove limit on number of tasks launched per scheduling step

[bveeramani]

Why are these changes needed?

In each Ray Data scheduling step, Ray Data launches tasks until it can't launch any more. To ensure that the progress bar updates frequently, #33952 made it such that Ray Data can only launch 50 tasks per scheduling step. However, this cause performance issues for large workloads.

This PR fixes the issue by removing the limit on number of tasks launched while still updating the progress bar frequently.

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

[raulchen]

I'm a bit concerned that this change may cause regression on latency-sensitive jobs.
Because now process_completed_tasks will be called less often.
Not sure how big the impact would be.
Maybe it's fine to merge it first and keep an eye on the release tests.