21755 - Fix directed request on subcollectives with rabbit connector.

The identity being used in the subscriptions hash for direct connections was
just using the host identity, not the collective also. Thus even though
the core mcollective was asking for subscription to a direct queue in each
sub-collective, they were all being hashed to the same identity, and thus
only the first one (in the list of subcollectives) was being listened to.

This causes the following issues (when using directed addressing):
. Commands using subcollectives (e.g. mco puppet status -T ldn) were failing
  to get replies (as the mco agents never saw the requests in the subcollective
  directed queue).
. Agents with a sub-collective list where the main collective was not the first
  entry never saw direct requests, as they only ever subscribed to the first
  queue for that subcollective
21755 - Fix directed request on subcollectives with rabbit connector

Update Changelog
22316 - MCO Plugin Packager produces more than one source artifact

In the past when invoking the plugin packager, multiple source artifacts
and builds would be run for every identified package.

This commit changes the behavior of the plugin packager to only build a
single source artifact and perform a single build.

The ability to keep build artifacts after the build process has
completed successfuly or failed has been added by passign the
--keep-artifacts flag to the packager.

Naming internally to the packager has also been improved. Iteration is
now referred to internally as revision and the --iteration option has
been renamed to --revision.

The #do_quietly?(true|false) method has been renamed to the more sane
 #perform_verbosely(true|false)

The #build_tool? has been renamed to #command_available?