Ensure stomp library gets installed on deb systems. Fix #15342
(Docs) Unify OS version info, update Puppet Enterprise info

- To make things easier for the release team, we moved the OS versions supported
  by our repositories into some central files, in the source/_includes directory
  of the puppet-docs repo. Mco docs can take advantage of this too.
- We're now shipping a PE with MCollective 2.x.
Docs: Fix misspellings of 'consistent'
maint: set up STDERR logging for the client as per intended defaults in the repo
Docs: Adjust a bunch of per-character intra-emphasis escaping

Individual _, *, and [ characters in words were sometimes being escaped with a
one-character code span. It's generally better to just wrap the whole word in a
code span, so this commit adjusts that as needed. This is part of a minor
cleanup across the docs to prepare for switching Markdown libraries.
22220 - add an install.rb file to mcollective

facter, hiera, and puppet all have an install.rb file, which does basic
installation of the project, with ruby library prereq checking, default config
and library file placement, and she-bang fixes for the ruby.  This simplifies
packaging, because the install.rb can be called in the install phase of the
various packaging methods for file placement instead of duplicating the logic
of copying files around.  This commit adds an install.rb to mcollective, ported
from the facter install.rb. It installs the .cfg.dist files as .cfg files in
$confdir, and plugins in /usr/libexec/mcollective/mcollective by default. This
install.rb does not support windows, because install.rb patterns are quite
different on Windows (and so is MCollective, I believe), and also because
Windows is foreign to me and I'd probably massacre it.
22220 - add an install.rb file to mcollective

Update Changelog
Merge pull request #46 from mfournier/tickets/master/15342

Ensure stomp library gets installed on deb systems. Fix #15342
Merge pull request #99 from nfagerlund/version_info

(Docs) Unify OS version info and plug Puppet Enterprise in more places
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
maint: Fix typo in ext/redhat/mcollective.spec

Reported/fixed by Jos Backus in
af5a719d-f434-451c-bc7e-0aedfa9e88ac@googlegroups.com
(docs) Tweak an unclear referent in keystores guide

Using "your" to refer to a new working dir seemed to imply that it had been
referenced before, and a user on IRC got confused.
Update: Change link to screencast list from blip.tv to official Puppet Labs account

The current MCollective video page has a duplicate version on the core puppetlabs.com site:

<http://puppetlabs.com/mcollective/screencasts>

In order to reduce the chance of duplicate content penalties, we want to make the version found on the docs site the canonical version and redirect traffic from puppetlabs.com to docs.puppetlabs.com. 

This change updates the link to the video list to use the YouTube account and playlist owned and maintained by PuppetLabs.com
Merge pull request #106 from nfagerlund/unclear_referent

(docs) Tweak an unclear referent in keystores guide
Docs: Add more explanation about the complexity of networkConnector elements

When explaining this to the PE team, I was reminded of many many gotchas lying
in wait. This makes the doc more wordy, unfortunately, but I think it adds
enough explanation that it'll be easier to get these right.
Merge pull request #109 from nfagerlund/activemq_network_connectors_again

Docs: Add more explanation about the complexity of networkConnector elements
(docs) Explain networkTTL attribute in network connectors

Existing docs seemed to imply that this was based on time, but it's actually
based on network hops.
Merge pull request #110 from nfagerlund/activemq_explain_network_ttl

(docs) Explain networkTTL attribute in network connectors
22316 - MCO Plugin Packager produces more than one source artifact

In the past when invoking the plugin packager, multiple source artifacts
would be created and multiple 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 passing 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 deprecated in favor --revision.

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

The #build_tool? method has also been renamed to #command_available?