pkg/cliwrappers: shell-escape log messages

[chmeliik]

The commands we execute may include shell control characters (most commonly whitespace). If we log the arguments separated by space, the log messages will look confusing and will not be copy-paste-able into a terminal.

Shell-quote the arguments that need quoting to make the log messages copy-paste-able. Use a similar approach as alessio/shellescape 1 or shlex 2 from the Python standard library.

Compared to those, use a slighly nicer escape style for single quotes. Our approach:

it's => 'it'\''s'

Their approach:

it's => 'it'"'"'s'

Assisted-by: Claude

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

ⓘ The new review experience is currently in Beta. Learn more

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[chmeliik]

This is in response to Qodo's review on an older PR, where I dismissed it, saying that hermetic builds will most likely need shell-quoting anyway.

I'm happy to have found a solution that does not require executing bash -c 'ip link set lo up && buildah build ...', but that means Qodo's point about unquoted shell strings in log messages still stands. This PR addresses it.