Update README commands for hiera-eyaml 2.x

https://github.com/TomPoulton/hiera-eyaml/commit/dabdcdc8284ff52b61b75f370d6a0ebda3dcb394#diff-0d0a4cc0a127ce66cc2cef430434000dL27
Set GPG home directory without an environment var

Previously, `gpg.rb` was setting `ENV['GNUPGHOME']` to set GPG's home
directory, which contains the GPG keyring used by Hiera eYAML GPG, for
the `ruby-gpgme` gem.

This caused problems on our Puppet installation as we have other Puppet
resources that use GPG, such as our [puppet-aptly] module among others.

Because the `ruby` process that runs Puppet also includes Hiera eYAML
GPG, the `GNUPGHOME` environment variable was present throughout the
Puppet run, meaning that our other Puppet resources were using Hiera
eYAML GPG's `:gnupghome` as their GPG home directory.

I was able to verify this by creating a temporary `exec` resource that
prints the environment variables visible to Puppet, i.e.:

    exec { 'test':
      command   => 'env',
      logoutput => true,
    }

This commit changes this so that we now specify the home directory using
`GPGME::Engine.home_dir`[1] rather than use an environment variable.

I'd hoped to add some Rspec integration tests to verify this, but hit a
number of issues, so resorted to testing this manually in Vagrant. The
environment variable is no longer set, and the GPG home directory is
correctly set. The environment now looks like:

    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: LANGUAGE=en_US:
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: TERM=vt100
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: PATH=/usr/lib/rbenv/shims:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: LANG=en_US.utf8
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: SHELL=/bin/bash
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: USERNAME=root
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: MAIL=/var/mail/root
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: SUDO_COMMAND=/usr/bin/puppet apply /var/govuk/puppet/manifests/site.pp --trusted_node_data --environment vagrant --modulepath /var/govuk/puppet/modules:/var/govuk/puppet/vendor/modules --manifestdir /var/govuk/puppet/manifests --hiera_config /var/govuk/puppet/hiera.yml
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: SUDO_USER=root
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: SUDO_UID=0
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: SUDO_GID=0
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: RBENV_VERSION=1.9.3
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: DEBIAN_FRONTEND=noninteractive
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: APT_LISTBUGS_FRONTEND=none
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: APT_LISTCHANGES_FRONTEND=none
    ==> cache-2.router: Notice: /Stage[main]/Main/Exec[test]/returns: executed successfully

[1]: https://github.com/ueno/ruby-gpgme/blob/fc299c9c1fb52ce64d288fce4a00db6e9ea79192/lib/gpgme/engine.rb#L63-L70
[puppet-aptly]: https://github.com/gds-operations/puppet-aptly
Ignore Gemfile.lock

Ignore `Gemfile.lock` so that it's not committed to source control.

`Gemfile.lock` is used by `bundler(1)`, whereas most gems (note 'gems',
not 'applications') are installed using `gem(1)` that has no ability to
read the `Gemfile.lock` file.

Please see:
http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
Correct an inaccurrate error message.

The error message formerly referenced the 'gpgpghome' key in hiera.yaml,
but the acutal key is 'gpg_gnupghome'.
Merge pull request #2 from mattbostock/improvements

[#80633966] Set GPG home directory without an environment variable