(MCO-179) Remove reference to package iteration in #package_information

When the iteration flag was renamed and deprecated one reference to it
remained in OspackagePackager#package_information.

This commit removes the last reference to iteration.
Merge pull request #161 from ploubser/bug/master/mco-173

(MCO-179) Remove reference to package iteration in #package_information
maint - update changelog
(packaging) Update buildrequires for rhel7

The systemd-units package is not available on rhel7, so this commit moves rhel7
and later into the same BuildRequires as f18 and later.
Merge pull request #163 from haus/maint/2.4.x/rhel7_fix

(packaging) Update buildrequires for rhel7
Merge branch '2.4.x'
(MCO-180) Release 2.4.1
maint - fix release notes
(mco-166)(packaging) Remove Fedora 18 from the default package builds
Merge pull request #164 from shrug/maint/mco-166/master

(mco-166)(packaging) Remove Fedora 18 from the default package builds
MCO-198 Connectors should not suggest heart-beats if the installed gem cannot do them.

This commit adds a new helper to the rabbitmq and activemq connectors
`stomp_version_supports_heartbeat?` which allows us to branch more
of the behavior around if the gem can do heartbeating.  We then use
this to not prompt you to enable STOMP 1.1 heart-beats if the
installed gem cannot cope with it.

It also softens the suggestion from a WARN to an INFO, as the user might not
want to enable them, especially if they are using activemq < 5.9 (or whatever
version of rabbitmq adds mature support).
Merge pull request #166 from richardc/MCO-198

MCO-198 Connectors should not suggest heart-beats if the installed gem cannot do them.
maint - update example plugin metadata

Make the plugin metadata consistent with the released service agent
distribution.

A further enhancement to the docs could call out that name is expected to have
a certain format (/^[a-z]+$/) and that it's used by other components like `mco
plugin`
MCO-191 Log receipt and contents of non-MESSAGE frames

Under normal operations @connection.receive is expected to return a
Stomp::Message object containing a MESSAGE frame.  If we get some other frame,
or no frame at all we still pass that up the layers and decode it, which can
lead to some quite dense error messages from the security provider layer.

Here we change the behaviour of the activemq and rabbitmq connectors
a little, to log these frames of unexpected type at WARN level,
with an inspection of the message as a DEBUG message.
Merge pull request #167 from richardc/MCO-191

MCO-191 Log receipt and contents of non-MESSAGE frames
Spelling error in activemq and rabbitmq connector plugins
Merge pull request #169 from fiddyspence/speeling_errer

Spelling error in activemq and rabbitmq connector plugins