Make `coder ssh --wait=no` more discoverable

Most people don't know that `coder ssh --wait=no` is a thing if the workspace startup scripts are still running and are under the perception that they must wait for it to do whatever its doing. I think `--wait=yes` is a reasonable default, but the message that's present that the workspace is still starting could also note that they can bypass it with `--wait=no`.