refactoring of character escaping in operation parameter values

There are potential issues with unescaping operation parameter values and command argument values that will be used as operation request parameter values.
The culprit is that these values are parsed twice: first, with the general command line parser and the second time with the value type parser (which depends on the type of the value: could be list, property list, DMR, etc). Both parsers support and may perform unescaping. Which may lead to confusions and issues like WFLY-161 or WFLY-1791 and then confusing conditions in the code.

The goal of this task is to not unescape parameter/argument values on the first parsing and leave it to the value type parsers. This concerns only parameter and argument value parsing, parsing of the other parts of operation requests and commands will remain as it is.