[k8s, attach-mode] build-, logs-, scripts-directories with whitespaces fail the build

Summary

When either

• BuildsDir
• Kubernetes.LogsBaseDir
• Kubernetes.ScriptsBaseDir

is set to something with a whitespace, the build fails.

This has been observed

• on linux (not tested on windows)
• with attach-mode (exec-mode seems to work fine)

(Not tested: CacheDir)

Steps to reproduce

• update a kubernetes integration test to
  • use attach mode
  • set either of the above mentioned config to something with whitespaces
• run that test
• see it fail / hang (depending on which knob you changed)

Actual behavior

Build fails or hangs

Expected behavior

Directories with whitespaces and other generally allowed chars should be supported

Relevant logs and/or screenshots

-

Environment description

• ran integration tests
• on linux
• against a cluster with linux nodes (only)

Used GitLab Runner version

da0fb9ebc4005fdd7b643fb9d453940a751ac096

Possible fixes

• Ensure we quote paths correctly
• Check on behaviour of windows
• Check if there are other config knobs which could lead to file paths with whitespaces and that like
• Check if this also happens for other executors than kubernetes