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
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
Fix syntax error in hubot.rb
Add a check for chef-server
Merge pull request #807 from tas50/master

Add a check for chef-server
Merge pull request #808 from aashley/master

Add rabbitmq-stomp-alive check
Modified the :long argument to be a ruby standard name.
Modified the :long argument to be a ruby standard name.
check-stats.rb: fix the issue of nil datapoints

Sometimes Graphite is lagging a bit. When that happens, the last data point in some (or all) metrics collected by this plugin will show as nil.

When calculating the average, nil is treated as zero. That throws the calculation out of balance. I've seen cases where the real metric was just a tiny bit over the threshold, yet it would not trigger the warning because the average was lowered by nil data points. I've had instances when that would continue for a long time, effectively masking the warning or the critical condition for up to 30 minutes, which is unacceptable.

For that reason, in the danger() function I've changed datapoints = metric['datapoints'].blah to throw out the nil points. Then the nil points are not artificially lowering the average anymore.

That's the first part of the diff.

The 2nd and 3rd part of the diff are related to the situation when all datapoints (not just the last one) in a metric are nil. In that case, the true status of this plugin is 'unknown', because that's what it is - we don't have any actual data points (they're all nil, which means missing data), so we acknowledge the 'unknown' status.
updating check-http.rb after feedback
Fail with unknown state if not running with elevated privs
Merge pull request #762 from paulhamby/master

Setting resp.body.size to 0 if there is no response body