Description of problem:
Environments where we are not able to use '/var/tmp' for example because of security concerns where people have configured noexec or otherwise are required to change the remote directory used for remote execution scripts.
When running:

# satellite-installer --foreman-proxy-plugin-remote-execution-ssh-remote-working-dir "<directory>"

This does correctly update the configuration file located at: /etc/foreman-proxy/settings.d/remote_execution_ssh.yml

However, this configuration change is ignored by Satellite and all jobs are still created in the default location of '/var/tmp'.

Version-Release number of selected component (if applicable):
Satellite 6.2.1:
rubygem-smart_proxy_remote_execution_ssh-0.1.2-2.el7sat.noarch
tfm-rubygem-smart_proxy_remote_execution_ssh_core-0.1.2-1.el7sat.noarch

How reproducible:
100%

Steps to Reproduce:
1. Run # satellite-installer --foreman-proxy-plugin-remote-execution-ssh-remote-working-dir "<directory>" (for example /tmp)
2. Run a job against a host.
3. Look at new directory.


Actual results:
Job will not be present in newly configured remote-working-directory.
If you check /var/tmp, foreman-* job folder and script will be present.

Expected results:
Need to use the special configuration specified via satellite-installer to change directory.

Additional info:
This likely also affected the local-working-dir configuration as well.