Manifests for managing the required packages and services on supported Linux
operating systems. These will be required for persistence.

Call the necessary commands from the provider to persist rules between
reboots. Tested on the following distros:

- CentOS 5.8
- CentOS 6.3
- Ubuntu 10.04
- Ubuntu 12.04
- Debian 6

Cavaets:

- Persistence may fail on the first run if Firewall resources are actioned
  before the Package resource.
- Older iptables-persistent doesn't support the restoration of ip6tables.
- ebtables cannot be restored.

Native persistence

autorequires from firewall and firewallchain resources to iptables and
iptables-persistent packages, when the appropriate provider is selected and
the packages are managed in the catalog. This will prevent failed rule
creation and persistence on fresh nodes where the packages may not be
pre-installed.

(GH-134) Autorequire iptables related packages

Debian is upstream of Ubuntu. Not the other way around. Would have affected
users of Facter <1.6.2 which doesn't have osfamily. Discovered while writing
tests, yey tests.

Basic coverage of protocol and OS detection. Including older and newer
Debian versions. Nearly all based on expectations since there aren't any
return values.

It's not valid to use `return` within a block. We could use `next []`,
however it's probably better form to just always return the array, whether
it's populated or not. This will stop the error:

    err: Got an uncaught exception of type LocalJumpError: unexpected return

When one of the listed providers isn't selected. Which is suitable, because
this autorequire won't be suitable to any other future providers anyway.

(GH-129) Replace errant return in autoreq block

Tests for #persist_iptables

Signed-off-by: Ken Barber <ken@bob.sh>

* ticket/master/release_020:
  Release 0.2.0

Signed-off-by: Ken Barber <ken@bob.sh>