Ensure alerts are generated if logging drops to 0

The ruby check uses "less than" or "greater than" operators not <= or
>=. Therefore a check looking for values below zero will never be
triggered by a value of zero. Zero is the lowest logging rate possible.
Merge pull request #681 from alphagov/fix-graphite-logging-rate-check

Ensure alerts are generated if logging drops to 0
Fix lint warning - optional param before required params
Only check logging rate in production.

Currently logging rate is so low in preview (and most likely staging)
that it is constantly triggering a critical alert in those environments.

This allows us to deploy to staging without constant critical alerts. If
we find we need the log check back however, Tim has suggested adding a
heartbeat.
Merge pull request #682 from alphagov/fix-lint

Fix lint warning - optional param before required params
Merge pull request #684 from alphagov/only-check-logging-rate-production

Only check logging rate in production.
Document that development-1 has the address 10.0.0.100
Disable dynamic scripting on elasticsearch

https://www.agileplannerapp.com/boards/47856/cards/7057

Prevent users from running arbitrary scripts via the API - this should
already be firewalled off, but disabling it is a good practice
Merge pull request #686 from alphagov/elasticsearch-dynamic-scripting

Disable dynamic scripting on elasticsearch
Replace lumberjack with logstash-forwarder

 - Upgrading in the hope we will stop logstash running out of memory and
   crashing. If not at least we are running a later version of the
   software. This PR
   https://github.com/elasticsearch/logstash-forwarder/issues/212 seems
   to suggest there may be issues with logstash forwarder. These
   logstash Jira tickets are also relvant -
   https://logstash.jira.com/browse/LOGSTASH-1253
   https://logstash.jira.com/browse/LOGSTASH-2168
 - Switch to the official elasticsearch logstash forwarder repo. There
   were a couple of issues with this which we would like to fix
   upstream -
 - For now add a symlink to correct the location
   the init script looks for the config file, as this is wrong in either
   the logstash-forwarder deb package or the puppet module
   https://github.com/elasticsearch/puppet-logstashforwarder/pull/12
 - There is an issue with file ordering in the puppet module. This means
   sometimes deploying using this module will fail
   https://github.com/elasticsearch/puppet-logstashforwarder/pull/13
 - The changes to our actual puppet code were renaming config params,
   using a different class, and renaming the defines to match the new
   puppet modules.
Add in code to remove lumberjack

This is a hack involving using the lumberjack module init and logshipper
manifests as skeleton from which we hang a lot of ensure absents. This
will be removed in a further clean up pr.
Add check for logstashforwarder being up

logstashforwarder is a process per box rather than per log file like
lumberjack. A single check per box should be enough.
Remove lumberjack process checks

no longer necessary following upgrade to logstashforwarder.
Create logstashforwarder directory

This is a workaround for a bug in the logstashforwarder module
that we're using.
Merge pull request #683 from alphagov/update-logstash-forwarder

Replace lumberjack with logstash-forwarder
Fall back to latest virtualbox version if no box

If no box has been built for the specific version of virtualbox used,
print a warning but fall back to using the latest available box.

This code gets executed when you have vmware installed, and would fail
to run the Vagrantfile. I have also tried with later versions of
virtualbox, and the box has worked even though the version doesnt
exactly match, so I think printing a warning is better behaviour than
bailing completely.
Merge pull request #685 from alphagov/vagrantfile-doc

Document that development-1 has the address 10.0.0.100
Merge pull request #675 from alphagov/virtualbox-matching-version-fallback

Fall back to latest virtualbox version if no box