Streamline supermarket::_runit recipe

By using the community runit cookbook, we can streamline the recipe.

* /etc/service is created in the runit recipe.
* runit_service resource handles all the resources for the services
* rename the template files so they can be used w/o fuss
* use the default_logger (replaces log/run resource from before)
Remove git references for dependent cookbooks

Using the git references for cookbook dependencies means that running
test kitchen will not reflect the same reality that using and
consuming the released supermarket cookbook has in our production
environment.

It is better when using Berkshelf to point to released artifacts - the
released versions of these cookbooks on supermarket itself, so that we
can ensure we're not pulling in potentially hazardous changes that
haven't been released.

Further, it is not clear why certain dependencies are declared here,
such as `ark`, `dmg`, or `7-zip`. Presumably because the entire
dependency graph of the community cookbooks was resolved with these
entries. That is superfluous as Berkshelf will get the community
versions.
rubocop/foodcritic linting cleanup

At some point, we'll have travis running against this cookbook, which will include foodcritic and rubocop checks. This commit cleans up the outstanding findings.

I disabled rubocop in the app_spec.rb because we're doing several things rubocop doesn't like, and trying to clean it up and test again is tedious.
Merge pull request #75 from opscode-cookbooks/jtimberman/lint-and-cleanup

[Cookbook] Linting and general cleanup
adding new URL vars
refactor how the .env.production template is generated