Since this cookbook builds software it should likely start depending
the core cookbook that provides the build tools for the environment

The ubuntu box on digital ocean was timing out and would not let connections come through.

Changed ark_test to ark_spec -- updated all references to it.
Changed node_properties to node_attributes
Reenabled Guard tests

Remove mention of checksum

The simple attr issue in the spec_helper is a dumb one so I'm going
to block it on the spec_helper as my uses are different and I don't want
to have the presence of an equals sign.

The other things were small line issues spread throughout.

Refactored to use each_with_object to quiet down rubocop as well.

Moved them into the fixture cookbook.

Similar to the `describe_recipe` I want to setup a helper that allows me to automatically take care of spec setup. Particularlly testing helpers is a bit trickier, at least for this gem, as it often times is relying on the "new_resource" which is available within the LWRP.

From my ruby days I like to see the folder path of the project be mirrored in the spec directory. I don't think I need to specify that they are "unit" tests by placing them in a special folder.

* tests the default recipe for all packages and default parameters
* tests the default recipe for CentOS

* Added color to the output
* Added an alias example so I can use `describe_recipe "ark::default"`
* The alias automatically loads the shared_context that gives me some
  helper methods like:

  ** chef_run - default run with no node_properties
  ** node - the chef_run's node.
  ** node_properties - blank, but can be overriden when needing to change the platform
  ** default_cookbook_attribute - lets me check for an attribute on the node

Adjusted all source file to address food critic recommendations

update README.md details about local file handling