Work out correct escaping of configuration variables in parameter file

[vinjana]

Configuration variables need to be passed through a shell-layer at different places in Roddy, e.g. in the wrapInScript.sh if when commands are remotely or locally executed.

The current approach to just use double quotes for configuration values (with some exceptions) is not ideal and results in misconfigurations. A better way needs implemented

• Consider using escaping instead of quoting.
• When to escape '$' characters -- sometimes they are used to reference other values? Or is this now completely solved by the in-Roddy evaluation of variable references?
• The actual pattern in-Roddy evaluated is '${...}'. By contrast, the '$...' pattern, without braces, is not evaluated by Roddy.
• Arrays cannot be passed as such to the called top-level script (due to a bash-bug) and are currently (an in the future) passed as space-separated strings. Each element needs to be subjected to escaping, while the complete array-string needs to be quoted and passed as string.

Continue these thoughts, and come up with a disciplined way for quoting and escaping that works and is simple enough for the users.

[vinjana]

Compare RoddyToolLib:bash-services (6e79d18).

[vinjana]

There is a reimplementation of the scaping logic that might be useful. See RoddyToolLib::RoddyIOHelpers.EscapableString, or consider using Apache Commons Text StringUtils.