[WIP][CORE]: Test fair dispatching

[Bye-legumes]

Why are these changes needed?

same as #44733 for debuging

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

[anyscalesam]

@Bye-legumes are you submitting this PRs to trigger our CI to see if test passes? cc @aslonnie

[Bye-legumes]

@Bye-legumes are you submitting this PRs to trigger our CI to see if test passes? cc @aslonnie

True, this PR can be ignore now as at that time there is a flaky test case that I think it cause by me but succeed on my side. So I set this to test which part caused that failed in CI. Currently that is fixed now. Sorry about that!