18513 - the --no-progress and --no-results flags do not work

The change in 18513 added proper support for --no-foo flags to the
application framework but in the process the booleans got swapped for
code like the rpc application.  The framework now behaves correctly but
the code in the app needs to be updated

This updates the logic to work in that case
18773 - when the rpc application fails to parse an argument exit on error

Previously when the arguments to the rpc app would fail to parse it
would just print a warning and continue, which would have unintended
outcomes

We now exit on argument parse error