Initial work adding puppetserver support

This is as much a request for feedback as a ready-to-merge PR, to get some discussion started on this. If this looks reasonable, I can add documentation and additional code, and rebase once the jfryman/nginx switch has been made.

This still needs the config settings from https://github.com/puppetlabs/puppet-server/blob/master/documentation/configuration.markdown to be managed
- where JRuby will look for gems
- path to puppet conf dir
- path to puppet var dir
- maximum number of JRuby instances to allow; defaults to <num-cpus>+
- enable/disable the CA service via trapperkeeper settings
- configure logging via logback

Additionally, it might be worth:
- adding a provider or other support for adding gems that the new jruby environment will be aware of
- facilitating JMX-based metrics collection (no idea how, just know it's possible)

As it stands, this will probably not work with the module's puppet dashboard functionality. Only the most basic aspects have been tested. Our Beaker tests have stopped working at some point but I'd like to merge jfryman/nginx and remote thin before putting the work into fixing them.

Changes:
Adds a dependency on stdlib
Add a few convenience entries to vagrantfile that I keep re-adding
manually while working
Needs work but appears to get a basic setup working on debian 7 and
add basic puppetserver test
centos 6
Add rspec tests for puppetserver
i would consider using ini_subsetting for this, i already use it with puppetdb: to splice their java_args with:
```yaml
puppetdb::server::java_args          : { '-Djava.net.preferIPv6Addresses' : '=true' }
```

(i'm just saying, i'll want to do that with puppetserver, too ;)