Hieraize and encapsulate parts à la boxen/puppet-redis

[donaldguy]

It's a lot of changes but I did my best to group them into clean changesets to make it easily reviewable

• Following the lead of boxen/puppet-boxen use ripienaar/puppet-module-data and undef parameters to allow easy overriding of parameters by organizations, as well as individual users (in particular allow moving back to default port without forking)
• Pass through a global ensure everywhere to allow whole cloth removal
• Return to a "custom" formula, Fixes Outputs several errors on subsequent boxen runs #5 ; its just the homebrew one with the shims, defaults, and plist removed from the formula (and bottles 😢 )
• Fail-fast parameter validation

Still to do (though can merge in my opinion without):

• add basic Debian support
• use that Debian support to make TravisCI go green despite No clear way to ensure module-data is loaded for (e.g.) puppet-boxen cardboard#13; I'd appreciate @dgoodlad's guidance on this if he already has any docs written up somewhere, but I'll probably figure it out by myself eventually

[rgabo]

Thank you for the great work @donaldguy, we're using both donaldguy/puppet-kafka and donaldguy/puppet-zookeeper with great success, very much appreciated.

Do you think you can cut a release here on GitHub of both Puppet modules? We've forked under sspinc for the sole reason of easily pointing to a tarball release from our Puppetfile. I would imagine that you're pointing go to your dev checkouts but we prefer:

github "kafka", "1.0.0", :repo => "donaldguy/puppet-kafka"

Thanks!