Clean up cookbook, prep for larger refactoring

[jeffbyrnes]

Some fixes/clean up, and prep for larger refactoring:

• Give the cookbook a name for use with Berkshelf
• Ensure consistency of code style, adhering to the Ruby Style Guide, using RuboCop
• Consistently use attributes for determining paths for Archiva files
• Use the apt cookbook to set up slightly out-of-date Debian-style systems properly for package installation
• Ignore some files properly (prep for uploading cookbook to Supermarket)
• Refactor the nginx_proxy recipe to work by including the default recipe
  • This is necessary because notifying a service that isn’t either defined in a recipe, or included from another one, prevents testing & is generally not solid pattern to follow (need your dependencies!)

[jeffbyrnes]

The Travis build fails because this branch doesn't have a .travis.yml. Bit of a misstep on my part, so don't let that put you off.

[jespada]

@jeffbyrnes tks, I'll look into it next week, have a nice week end !

[jespada]

@jeffbyrnes thanks, we should add some spec test, and .kitchen file as well, at the momento I'm not using this cookbook, but I'll see if I have time to add those, in any case PR are welcome :)

[jeffbyrnes]

@jespada yep; I've got a whole separate branch on our side that has tests, etc., that depends on this first. Now that it's merged in, I can spruce that branch up for public consumption & open a new PR.

Thanks!