ruby 1.9 and above was not really supported before puppet 3.x [1] so don't
test any of these combinations. These combinations actually were
excluded before, but the matrix got messed up in the previous
commit.

[1] https://docs.puppetlabs.com/guides/platforms.html#ruby-versions

The environment variables inside Gemfile changed (adopted to puppet
module generate) so we also have to modify the travis file to set the
correct environment variables when testing against specific
puppet/facter versions

To be able to release the module puppet module generate was used to get
a basic sketch of the Gemfile and metadata.json file. Also added a
changelog as puppet forge modules are versioned.

* genebean-readme-update:
  Added info on how to find the keyID to the readme file.

Running the specs with rspec3 leads to the following deprecation
warning:

    Using `should` from rspec-expectations' old `:should` syntax without
    explicitly enabling the syntax is deprecated. Use the new `:expect`
    syntax or explicitly enable `:should` instead

So switch to the new expect syntax

Since the specs for the type do not use any provider features we do
not have to create a fake provider.

PuppetLabs has released a seperate gem to make writing spec tests easier
(puppetlabs_spec_helper). Using this gem makes a lot of files obsolete
that were initially copied form the puppetlabs/puppet project.

If there is currently no key present in the RPM keyring rpm -q returns
with a non-zero exitcode. This case is now handled properly so no
error message is shown when running puppet.

Because we never really execute rpm and are only testing the provider we
are never asked suitable? so we can just drop a few stubs of FileTest

The rpm_key type was renamed to rpmkey pretty early but the spec
directories should also reflect the new name.

The new type can be used to describe an imported gpg key

Add README and copy the necessary testframework from the puppet codebase