Comment 2 for bug 2055806

This is a follow-up to the problems reported in the following thread that already discussed an issue with socket activation for the ssh.service.

SSHd now uses socket-based activation (Ubuntu 22.10 and later)
https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-ubuntu-22-10-and-later/30189/4