Issue directing script output to pipeline for systems that mount the shared filesystem with different filesystem types
## Summary
Jacamar CI job output for build step isn't being displayed in pipeline, but before_script and after_script commands are correctly displayed. This happens with both PBS and Slurm executors. Shell executors work as expected
## Steps to reproduce
Run jacamar on a system with the compute nodes mounting /home via lustre, but the node currently running jacamar/gitlab runner mounts /home over NFS (coming from a node that mounts $home via lustre and re-exports it via NFS)
This works as expected for gitlab and jacamar setups that write to a NFS or local $HOME.
by adding `retain_logs = true`, I can confirm that output shows up in the files (checking from the jacamar/gitlab runner machine)
## Expected behavior
Job outputs should show up in the pipeline regardless of how the shared filesystem is mounted.
## Possible fix
<!-- Possible source of the bug or potential steps to fix. -->
our sanitized gitlab-runner.toml
```
listen_address = "0.0.0.0:9253"
concurrent = 10
check_interval = 0
log_level = "debug"
shutdown_timeout = 0
[session_server]
session_timeout = 1800
[[runners]]
name = "HPC_HOST_NAME"
url = "https://GITLAB_FQDN/"
token = "TOKEN_GOES_HERE"
executor = "custom"
[runners.cache]
MaxUploadedArchiveSize = 0
[runners.custom]
config_exec = "/opt/apps/Module/jacamar/0.16.0/bin/jacamar-auth"
config_args = ["--unobfuscated", "config", "--configuration", "/home/gitlab-runner/.gitlab-runner/jacamar-config.toml"]
prepare_exec = "/opt/apps/Module/jacamar/0.16.0/bin/jacamar-auth"
prepare_args = ["prepare"]
run_exec = "/opt/apps/Module/jacamar/0.16.0/bin/jacamar-auth"
run_args = ["run"]
cleanup_exec = "/opt/apps/Module/jacamar/0.16.0/bin/jacamar-auth"
cleanup_args = ["cleanup", "--configuration", "/home/gitlab-runner/.gitlab-runner/jacamar-config.toml"]
```
jacamar-config.toml
```
[general]
executor = "slurm"
data_dir = "$HOME"
retain_logs = true
[auth]
downscope = "sudo"
[auth.logging]
enabled = true
```
issue