Use the puppet default bindaddress

Issue #69 makes a valid point.  Essentially the bindaddress does not
behave as expeted when IPv6 is not configured on the client.
Added param dns_alt_names
Added param autosign
Switch nginx modules
Switch to jfryman/puppet-nginx from ploperations nginx module
Remove unused unicorn init script
This does not appear to be in use; the init script for unicorn puppetmasters comes from the unicorn module
Convert thin and unicorn to use jfryman/nginx
This replaces use of the ploperations/nginx module with the jfryman/nginx module
this does not fix the known issue of unicorn puppetmasters currently failing because of a missing HOME environment variable. That issue predates this commit.
Fix thin dependency order
Ensure that webrick puppetmaster is stopped before starting nginx; caused errors on first run
Add hosts entry to thin test
Add 'puppet' host entry to simplify testing of a puppet agent run
Improve management of the pupept config dir

This code merely leverages the parameters to create the directory and
avoids hard-coding paths in places.
Switch to using includes
Use non-module_data jfryman-nginx
Switch jfryman-nginx in fixture to last commit hash before module_data was introduced
Bump puppet version from 3.6 to 3.7 in case
Tune group and user for OpenBSD

This work ensures that the agent configuration will use the group and
user native to the given platform for permission handling.
Fix broken nginx-unicorn support
addresses puppet-puppet issue 119 by switching from using the default
location in the vhost to using an explicitly defined location, in
order to avoid the default headers that cannot be unset on the default
location.

Add beaker tests to test for this problem
Note that the beaker tests for this pass, but there are still failures.
I think it's better to get this fixed and add tests rather than blocking
on fixing everything.

Extend vagrantfile
Not specific to this issue, just came up as a convenience