…hon#111402)unistd.h is needed by alarm() and pause() functions.

…ython#110582)

…thon#110884)- `ThreadedChildWatcher.close()` is now *officially* a no-op; `_join_threads()` never did anything.- Threads created by that class are now named `asyncio-waitpid-NNN`.- `test.test_asyncio.utils.TestCase.close_loop()` now waits for the child watcher's threads, but not forever; if a thread hangs, it raises `RuntimeError`.

* Include Python version in cache.config key, after Python setup* Remove EOL 3.7 from branch triggers

…GH-111336)* Try to fix asyncio.Server.wait_closed() againI identified the condition that `wait_closed()` is intendedto wait for: the server is closed *and* there are no moreactive connections.When this condition first becomes true, `_wakeup()` is called(either from `close()` or from `_detach()`) and it sets `_waiters`to `None`. So we just check for `self._waiters is None`; if it'snot `None`, we know we have to wait, and do so.A problem was that the new test introduced in 3.12 explicitlytested that `wait_closed()` returns immediately when the serveris *not* closed but there are currently no active connections.This was a mistake (probably a misunderstanding of the intendedsemantics). I've fixed the test, and added a separate test thatchecks exactly for this scenario.I also fixed an oddity where in `_wakeup()` the result of thewaiter was set to the waiter itself. This result is not usedanywhere and I changed this to `None`, to avoid a GC cycle.* Update Lib/asyncio/base_events.py---------Co-authored-by: Carol Willing <carolcode@willingconsulting.com>

…classes. (python#110655)

…er (pythongh-111441)

…ngh-111444)

…ngh-111449)