Do not hardcode used environment in template

[Ganneff]

This avoids triggering the notify (and as such a long log4jscanner
run) on file changes just because one puppet run is in a different
environment (say, for testing).

To allow this, we have to find the environment used in the script.
We first parse the last runs report (if exists), and if that fails we
fall back to directly asking puppet what it thinks. This way we
support both, standard environments and those that somewhat drive
around the normal mechanism of setting the environment for the agent.

This Fixes #16

[CLAassistant]

All committers have signed the CLA.

[puppet-community-rangefinder]

log4jscanner is a class

that may have no external impact to Forge modules.

This module is declared in 0 of 578 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[Ganneff]

Closed in favor of #20