The logger setup was confusing when using --log-file-level=DEBUG,
showing this debug-level output inside default --log-cli-level=INFO output,
but without the debug context that only went into the logfile, and without
any hint of what kind of output it was.

This makes it use the same logger as all other debug output, preventing it
from appearing in the wrong place, and adds a marker to hint it is output
data - at the same time fixing a potential formatting issue, where
arbitrary ssh output lines were interpreted as *format strings*.

Signed-off-by: Yann Dirson <yann.dirson@vates.tech>

…logs"

This reverts commit 5b97ff0.

With the unified logger the original issue is not there any more.

Signed-off-by: Yann Dirson <yann.dirson@vates.tech>

They won't make it to the console unless required by --log-cli-level, but
now pytest will show them systematically when a test fails.

Signed-off-by: Yann Dirson <yann.dirson@vates.tech>