Restore retire workers API

[fjetter]

#8935 accidentally changed the public API for retire workers. I thought this was used only internally but it is used by client.retire_workers as well (and of course whenever the request handler is being used directly)

This should restore the API without reverting the changes to the logged event that was the primary intention of #8935

[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 23m 7s ⏱️ + 15m 6s
 4 130 tests ±0   4 014 ✅  - 1    110 💤 ±0   6 ❌ +1 
47 692 runs  ±0  45 533 ✅  - 2  2 122 💤 +1  37 ❌ +1 

For more details on these failures, see this check.

Results for commit 97544d5. ± Comparison against base commit 0d905d5.

♻️ This comment has been updated with latest results.

[jrbourbeau]

Thanks @fjetter

Looks like we need to update distributed/tests/test_active_memory_manager.py::test_RetireWorker_with_actor_proxy too

diff --git a/distributed/tests/test_active_memory_manager.py b/distributed/tests/test_active_memory_manager.py
index bcc0d48d..1bc9855b 100644
--- a/distributed/tests/test_active_memory_manager.py
+++ b/distributed/tests/test_active_memory_manager.py
@@ -1250,7 +1250,7 @@ async def test_RetireWorker_with_actor_proxy(c, s, a, b):
     assert "y" in b.data

     out = await c.retire_workers([b.address])
-    assert out == (b.address,)
+    assert out.keys() == {b.address}
     assert "x" in a.state.actors
     assert "y" in a.data

[jrbourbeau]

I could be missing something, but it looks like we're adding back the verbose thing removed in #8935 now. Just wanted to make sure that's intentional