use node.default to be more respectful of users

Using node.set has several problems:

  * It stores the data on the chef server (and we use node.set for apikeys. Bad!)
  * It means the user has to at least set a normal attribute on their node/role/env
Merge pull request #38 from racker/jordane/dont_set_normal_attributes

use node.default to be more respectful of users
warn user if apikey or username set as normal
Merge pull request #39 from racker/jordane/dont_set_normal_attributes

warn user if apikey or username set as normal
Fix syntax error in default.rb
fog is required in the default recipe
add fog version attribute
bump version for move to fog
move to fog gem
removed rackspace-monitoring-rb and got entities and agents working with fog
installing from file to get around rubygems fog-1.14.0 not matching gits fog-1.14.0
fixes to fog gem, which are in a pull request to fog
move to fog 1.15.0
Cleaning up hash arguments for readability
Fixing the fixed formatting
add changelog, update readme
remove unneeded fog-1.14.1 local gem
update metdata to recommend chef_gem cookbook
switch to Opscode::Rackspace::Monitoring for includes to match rackspace-cloud cookbook formatting
this caused the alarm issues. Fog is expeting check not check_id.