support to clean worker table with maximum_gcs_dead_worker_cached_count

[zszheng]

Why are these changes needed?

If there is no cleaning mechanism, the Worker table will continue to grow with each new Worker added to the cluster. Over time, this will lead to the issues mentioned by ISSUE（https://github.com/ray-project/ray/issues/49029）, thereby affecting the stability and performance of the Ray cluster.

Related issue number

#49029

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