Flexibility to have multiple hipchat configs

Please refer: https://github.com/sensu/sensu-plugin/issues/66

Currently, the handler assumes that there will be a json file which will have "hipchat" as the top-level key in the json. Due to the same, we can only have one hipchat configuration for using with hipchat.rb.

The above changes the behavior by taking in an optional config json top level key name while invoking the handler (Instead of "hipchat.rb" you invoke "hipchat.rb --jsonConfig <config top level key>" as the handler command).

In this way, we can have multiple handlers defined with different hipchat configurations such as different hipchat rooms or different from fields.

Note: As it is an optional parameter, it will just work fine with the existing hipchat.json method (Backward compatible :) )
Removed trailing whitespace.
Fixed review comment around variable name change.
Changes to have multiple mail configs
Replaced tabs with whitespace
Setting resp.body.size to 0 if there is no response body
Added hardware, disk, and raid failure checks.
Add --short_output option

--short_output restricts the output to only the highest alert per target
returned
Style cleanup
Add Hubot handler for sensu
Added Hipchat extension
Added check-stats.rb graphite plugin.
Throw an unknown status if graphite didn't return parseable data
Fixed embarrassing mistake
Fix syntax error in hubot.rb
Document the EMBEDDED_RUBY option for ombinus Sensu installation
Moved check-raid.rb to raid directory
Made check-stats executable and made the options more readable
Merge pull request #805 from edzhelyov/embedded-ruby-doc

Document the EMBEDDED_RUBY option for ombinus Sensu installation
Merge pull request #798 from S2Games/check-stats

Added check-stats.rb graphite plugin.