18437 - mco plugin doc broken for data plugins

In the past mco plugin doc failed when passing a data agent as the
parameter.

In this commit mco plugin doc will correctly display the meta and help
data for a data plugin.
18437 - mco plugin doc broken for data plugins

Update changelog
18466 - Data::Result#method_missing raises incorrect exception

When calling a method on a class that does not exist ruby expects a
NoMethodError to be raised.

The Result::Data class has a method_missing that allows access to data
items via faked methods and it checks for unknown data items and raises
an error but unfortunately it raised the wrong exception type.

We now raise NoMethodError as expected
18259 - Release 2.3.0

 - Release notes and changelog tweaks
 - Update the Rakefile for 2.3.0-1
maint: small formatting fixes in the release notes page
18258 - Release 2.2.2

Update master branch docs to reflect release 2.2.2
maint: Fixed typo
18499 - Docs: Fix missing => in agent DDL example
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
Update website/terminology.md

Typo: wikpedia -> wikipedia
19105 - default_discovery_method and others isnt correctly handled by the RPC::Client

Previously we used settings like default_discovery_method before
actually initializing the settings and so they would be set to nil

This caused a few hard to detect issues like discovery being used for -I
discovery flags that supplied a specific host where normally it would
use this information as discovery data

This re-arranges things a bit to start the code Client early on in the
RPC client initialization