To install Chocolatey, we need to take a dependency on the powershell
module. To be able to validate user input, it's best to take a
dependency on stdlib as it has quite a bit of built-in validation.

This is the same script found at https://chocolatey.org/install.ps1.

Allow installing chocolatey with a custom package location. Also allow
using the built-in windows shell to unzip the package. The original request for
this had the ability to use the built-in Windows shell to perform the unzipping
and it keeps folks from having to download an external executable by
default. Allow 25 minutes for it to finish.

Depend on the windows_env module for path update changes. This is to
ensure they are propagated on the same run you install Chocolatey in.

For spec testing, ensure that the `.fixtures.yml` has all modules that
are dependencies listed.

Allow install timeout to be configurable. Move all variables to
params.pp.

Ensure that the windows environment variables are set and are present.
This should also allow Chocolatey to be installed and used on the first
run of Puppet as it will refresh the PATH environment variable so that
suitability is redetermined[1]. This stems from an original conversation[2] with
a few community members and @joshcooper about suitability determination not
being cached in newer versions of Puppet.

[1] https://docs.puppetlabs.com/guides/provider_development.html#suitability
[2] https://groups.google.com/d/topic/chocolatey/0hPNtAMmhNM/discussion

This includes a custom fact for chocolatey's installpath. It will attempt
to read the environment variable for ChocolateyInstall from the registry
and default to 'C:\ProgramData\Chocolatey' if it is not found. This allows
Chocolatey to look at an existing installation by defaut.

The `$chocolatey::params::install_location` variable will default to
this custom fact, but can be overridden when declaring the class.

Introduce init.pp and set install.pp as a private class.
This allows the benefit of `include chocolatey` without needing
to think about how to install Chocolatey and do any additional
setup steps. This was suggested by @reidmv at
chocolatey-archive#76 (comment).

As an artifact of adding `assert_private()`, move stdlib
requirement to at least 4.6.0.

Ensure rspec dependency is at least 3.0, but less
than 3.3.

For Puppet older than 3.5.0 on Windows, a facter version at or under
1.7.5 should be selected for greatest compatibility when requesting
a gem puppet version and if a facter version has not been specified.

Set autouninstaller to true by default.

Validate that the parameters being passed in meet
the expectations.

Similar to Facter for Puppet versions less than 3.5.0,
if Hiera version hasn't been set, use a version that
was released with older Puppet versions.

Additionally ensure that both facter and hiera are
treated this way no matter if the Puppet is on Windows
or on *nix.

Contain is not a supported keyword prior to Puppet 3.4.0.
If less than 3.4.0, use the anchor pattern instead.

Add examples of usage surrounding the installation of Chocolatey to the
readme and document the classes/parameters.

Confine boundaries on upper versions of dependencies. This allows
better compatibility as the major version barrier is a known semantic
versioning boundary for incompatible changes.

Expose a custom fact about Chocolatey's version. Do not
attempt to do configuration in versions of choco less
than 0.9.9. This does mean a second convergence will be
required to apply the configuration settings.

Add documentation for the new facts this module produces.