18434 - when showing failed data using printrpc we should not show all the data for that reply

Previously the DDL didn't fill in all default data so often when
result.fail was called the half baked data was useful to display by
default, now it's not.

This adjusts things to not show the data on a 1 statuscode by default
but it is still available via -v
18447 - Call out application specific options better in --help

Previously the --help output would not clearly call out application
options from rpc options from common framework options, this makes it a
little bit better but we really need to rethink our approach to option
display in general
18758 - Packages created by the plugin packager need to require specific versions

In the past packages created by the plugin packager would have a >=
dependency on the common package.

This commit changes this to a = dependency.
18758 - Packages created by the plugin packager need to require specific versions

changelog
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