🐋 investigate using psusan instead of sshd to remove authentication awkwardness

[DerekNonGeneric]

What we are currently doing regarding SSH daemon setup and its associated scripts in the devcontainer is certainly an inconvenience, quite possibly unnecessary, and warrants further investigation as none of this authentication we are currently requiring of developers is of any use on their local machines.

There appears to be an excessive amount of setup in the route we originally went. Can we do better?

Refs: https://github.com/microsoft/vscode-dev-containers/blob/main/script-library/sshd-debian.sh

This involves more setup: you have to invent an SSH host key for the container, accept it in the client, and deal with it being left behind in your client's host key cache when the container is discarded. And you have to set up some login details in the container: either configure a password, and type it in the client, or copy in the public half of some SSH key you already had. And all this inconvenience is unnecessary, because these are all precautions you need to take when the connection between two systems is going over a hostile network. In this case, it's only going over a kernel IPC channel that's guaranteed to go to the right place, so those safety precautions are redundant, and they only add awkwardness.

Refs: https://manpages.debian.org/unstable/putty-tools/psusan.1.en.html