Bug 1851382

Description of problem:
When ssh debug logging is enabled, it prints only the facility which emitted the message, not the message itself.

Version-Release number of selected component (if applicable):
rubygem-smart_proxy_remote_execution_ssh-0.3.0-3
rubygem-foreman_remote_execution_core-1.3.0-1


How reproducible:
Always


Steps to Reproduce:
1. Set ssh_log_level to debug in /etc/smart_proxy_dynflow_core/settings.d/remote_execution_ssh.yml
2. Restart smart_proxy_dynflow_core
3. Run a REX job
4. Watch /var/log/foreman-proxy/smart_proxy_dynflow_core.log

Actual results:
The log contains logs like 
socket[2abe13ae57f8]socket[2abe13ae57f8]net.ssh.connection.session[3fcbf60ee3e8]net.ssh.connection.channel[3fcbf6108dec]socket[2abe13ae57f8]net.ssh.connection.channel[3fcbf6108dec]socket[2abe13ae57f8]socket[2abe13ae57f8

(also hitting BZ1851379)

It does not show what is actually supposed to be logged, only that a session or a channel emitted a log message.

Expected results:
Log messages like
net.ssh.transport.algorithms[2b0600e23494]: negotiating algorithms
net.ssh.transport.algorithms[2b0600e23494]: negotiated:
* kex: ecdh-sha2-nistp521
* host_key: ecdsa-sha2-nistp256
* encryption_server: aes256-ctr
* encryption_client: aes256-ctr
* hmac_client: hmac-sha2-512-etm
* hmac_server: hmac-sha2-512-etm
* compression_client: none
* compression_server: none
* language_client: 
* language_server:


Additional info: