13576 - Change FPM version in packager

Changes to FPM's api in version 0.4.4 has broken the mcollective plugin packager application.

The required gem version has been set to 0.4.3, the last stable version, until we drop our
dependency on FPM in the near future.
13576 - Change FPM version in packager

main: fix failing test
13320 - Package info raises an exception

When running plugin info an exception will be raised if any of the
default package types are nill.

Empty package types are now removed from the packagedata hash
before info is displayed on screen.
13577 - Plugin Packager file names

Packages generated by the plugin packager do not currently include
version, iteration or architecture.

Package file names now include the version and iteration numbers,
noarch for rpms and all for debs.
13596 - Plugin Packager fails when plugin name has a space.

The plugin packager fails to build packages if a plugin name in
the ddl or one from the command line contains spaces.

The plugin definition classes now correctly checks on creation
if the name contains spaces and replaces them with underscores.
  13597 - mco plugin doc output needs to be formatted better.

  Currently when mco plugin doc is called the output isn't clear.
  Its unspecified whether the application was successful and
  what the user should do next.

  Added a more descriptive message to indicate failure when mco
  plugin doc is run without an agent being specified.

  Formatting has also been cleared up by adding a new line at the
  end of the output.
13615 - The SSL security plugin should use the MCollective::SSL class

The SSL plugin predates the MCollective::SSL class but the intent is
that all crypto in the framework be done in the M::SSL class so that
testing and bug fixes in this critical code is contained.

This commit signature verification logic to the M::SSL class with tests
and adjust the SSL security plugin to use the M::SSL class for its
crypto needs.  The SSL security plugin gains access to the fixes for the
Ruby core SSL key reading bugs via the same
13599 - Release 1.3.3

Release notes, Rakefile and Changelog update for release 1.3.3
maint: markup fix in release notes
13654 - Add BuildRequires on ruby to spec file

Without the BuildRequires on ruby, the chroot built for mocking will have no
ruby and will have ruby sitelib undefined in the spec file, which will result
in files being installed to top level directories instead of
/usr/lib/ruby/site_ruby/... This fix adds that BuildRequires to the spec file.
13872 - Ruby 1.9.1 RbConfig compatibility

In ruby 1.9.1 and early 1.9.2 development series the RbConfig or
Config classes were not loaded automatically by ruby but in earlier
and later ones it is.

This makes sure we load it before trying to create compatability aliases
for it thus fixing at least one issue with earlier Ruby 1.9
13324 - 'rake' breaks on the mac

Changed 'sed --in-place' to 'sed -i' to unbreak build on the mac
13324 - 'rake' breaks on the mac

Update changelog
13043 - mcollective init script for Debian/Ubuntu

New Debian init script that uses LSB helpers to properly start
and stop the mcollective daemon
13043 - mcollective init script for Debian/Ubuntu

Update Rakefile to replace the default mcollective.init with the debian one
Update changelog
13939 - Fix instances of "parenthesize argument(s) for future version" on 1.8.5

Fix various cases of "parenthesize argument(s) for future version"
errors in the spec tests for ruby 1.8.5
14056 - mention 'mco help foo' in the default output of 'mco'

The command list from 'mco' was unsorted and kind of ugly with
no line breaks, prone to line wrapping and did not give the user
information on how to obtain help for commands.

It's now sorted, listed in columns and mentions how to get help
13978 - Remove unnecessary dependency on most recent stomp versions

The new stomp gem defines various helpful Stomp::Error::* classes which
help us handle various types of failure better where in the past it
was all just the same kind of exception.

In adding those to rescue blocks we inadvertantly forced that everyone
use the newest gem which is not what we want.

This commit detects older gems and create dummy constants for these new
errors which will never be used with older gems and effectively noops
those rescue blocks.

This is temporary code at best, soon as the 1.2.x series Stomp gem is
wider tested we will require at least 1.2.2.
maint: rename spec files so they are matching the pattern in the Rakefile
maint: improve some really bad tests that polluted the namespace and
       order dependency in the tests.  Now works reliably with
       rspec --order random