Remove dump cluster from gen_cluster

[fjetter]

I don't see a lot of value for having this still around. However, it is spamming the working directory and makes test execution (if failed) much slower.

[github-actions]

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

    25 files  ± 0      25 suites  ±0   10h 9m 33s ⏱️ - 6m 10s
 4 099 tests  -  6   3 981 ✅  -  3    113 💤 ±0  5 ❌  - 3 
47 366 runs   - 72  45 232 ✅  - 69  2 129 💤 ±0  5 ❌  - 3 

For more details on these failures, see this check.

Results for commit f97062d. ± Comparison against base commit 3075b08.

This pull request removes 6 tests.

distributed.tests.test_utils_test ‑ test_dump_cluster_state
distributed.tests.test_utils_test ‑ test_dump_cluster_state_nannies
distributed.tests.test_utils_test ‑ test_dump_cluster_state_no_workers
distributed.tests.test_utils_test ‑ test_dump_cluster_state_timeout
distributed.tests.test_utils_test ‑ test_dump_cluster_state_unresponsive_local_worker
distributed.tests.test_utils_test ‑ test_dump_cluster_unresponsive_remote_worker

♻️ This comment has been updated with latest results.

[hendrikmakait]

CI isn't happy with this PR, need help fixing this up?

[jrbourbeau]

Thanks @fjetter. I left one non-blocking comment but otherwise this LGTM

[jrbourbeau]

Another option is to leave this functionality around but still disable it in gen_cluster. I'm not sure how much value there is to having dump_cluster_state around for diagnosing tricky deadlock situations.

[fjetter]

The functionality itself is part of Client. I'm not entirely sure what this utility function offers but I'd rather not maintain it.