Log client addresses in scheduler lifecycle messages

[peter941221]

Summary

• include the client's remote address in the scheduler log messages for client connect, remove, and close events
• store the peer address on ClientState so the same address is available throughout the client lifecycle
• add a scheduler test covering the new log output

Closes #8000

Testing

• python -m py_compile distributed/scheduler.py distributed/tests/test_scheduler.py
• not run: python -m pytest distributed/tests/test_scheduler.py -k client_connection_logs_include_address (local environment is missing dask, so pytest fails during config import)

[github-actions]

Unit Test Results

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

    30 files   -     1      30 suites   - 1   10h 21m 28s ⏱️ - 21m 36s
 4 075 tests +    1   3 969 ✅ +    1    104 💤 ± 0  2 ❌ ±0 
57 742 runs   - 1 389  55 375 ✅  - 1 321  2 365 💤  - 68  2 ❌ ±0 

For more details on these failures, see this check.

Results for commit d42d844. ± Comparison against base commit d8fabe2.

♻️ This comment has been updated with latest results.