Vagrant support

I haven't actually changed anything, but simply added a straight up port to vagrant. Not sure if you've built it lately, but it seems that quite a few modules have broken packages, since they're `ensure`d at a specific build that is now out of date. (And as far as I've learned, sysadmins don't tend to lock down to build numbers. The assumption seems to be that if it's in the apt repo, then it's good to go. "Pinning" is usually only done when there are specific conflicts that apt gets confused with or doesn't recognize.)

Was looking at the community modules, and they just seem to `ensure` "present":
https://github.com/puppetlabs/puppetlabs-mysql/blob/master/manifests/server.pp#L19

Speaking of community modules, I've prepped this branch for librarian-puppet support, which is essentially a package manager for puppet modules that resolves dependencies into a lockfile (kinda like composer, if you're following that is php land)

Thinking that I can start converting some of your custom puppet modules into leveraging the  popular community modules, which will hopefully remove lots of overhead and give you easy access to snazzy new features. Would you mind if we took that approach?

Anyhow, like I said, psyched to help out with this project :)