Include Augeas

The official elasticsearch puppet module uses Augeas to fiddle with
system defaults for elasticsearch. We need to include it in bootstrap vs
in our puppet modules because puppet expects it to exist before it runs
to enable the augeas resource provider.
Elasticsearch to official module and new version

The GDS module we were using has been deprecated and moved into the
attic and we have been meaning to move to it for a while.

The new module has the concept of a central installation with 1 or more
instances that are running on the node. We have configured 1 instance
with the same configuration as our existing elasticsearch setup.

The empty hash for the config param to the ::elasticsearch class is
there to stop it being a string, which blows up puppet.

We have included the apt repo in our manifest vs using manage_repo as
the later caused a dependency cycle in our code.

Templates need to be included when the instances are setup as they will
curl their configuration into the instance and if it is not setup and
running it will break.
Add logs-elasticsearch-3 to cluster_hosts

Not sure why it wasn't there and probably should have been.
Change path to elasticsearch log for OOM check

Given the new way the official elasticsearch module structures instances
of elasticsearch our logs have changed location. This starts tailing the
correct location.
Update kibana version

The version we were using is no longer compatible with the newer version
of elasticsearch. This updates the version and cleans up some of the
code in the performanceplatform::kibana class.
Remove the erasure of the elasticsearch rotate

As we have started with fresh boxes this no longer needs to be here.
Include estools

The deprecated elasticsearch module used to include these tools. We
still need them to rotate out our indices so we should install them
ourselves.

This relies on the following PR being merged:

https://github.com/alphagov/estools/pull/7

As the old version of pyes used by the tools had issues.
Roll elasticsearch logs based on size

log4j, the underlying elasticsearch logging library, can't roll logs
daily and remove some after a certain date. Using a rolling file
appender and limited on the size of logs gives us both the ability to
remove and ensures that our logs do not blow up our disk if something
gets over excited.
Merge pull request #632 from alphagov/feature/new-elasticsearch

Feature/new elasticsearch