fix encode (output) for oldlogstashjson codec.

It was referencing the obj variable which didn't exist
Write a failing test when prefix & include/exclude keys are used together
Fix a bug where field goes missing if include/exclude is used with prefix
Fix fail() invocation if no config file is given.
Use latest kibana for the flatjar. (LOGSTASH-1416)
Replace older event.type with event["type"]
Shrink port range to 9300-9305. This was done after a discussion with
kimchy about the problem this portrange thing tries to solve - mainly,
this helps avoid logstash when started first from *not* finding the
local elasticsearch server (if there is one) because LS took 9300
forcing ES to take 9301 and logstash never finds it.
Merge pull request #665 from turtlebender/feature/fix-oldlogstashjson-encode

fix encode (output) for oldlogstashjson codec.
When doing number validation, leave a  Numeric as-is and only try to do
float/int conversion on strings. (Fixes LOGSTASH-1441)
Merge pull request #705 from logstash/fix-numeric-handling-in-config

When doing number validation, leave a  Numeric as-is and only try to do
- (backwards compatibility) start working on making 'format' setting act as a codec setting.
- add deprecation message for the 'format' setting
- correctly load the codecs for format's setting
- don't use deprecated things
Merge pull request #706 from logstash/format-backwards-compat

Format backwards compat
Merge pull request #673 from shadyabhi/fix_prefix_and_include_exclude_keys_related_bug

Fix prefix and include exclude keys related bug
Add 'workers' setting to output plugins.

This allows you to run multiple workers for a single output in cases
where CPU or network IO are bottlenecks in a single output. The
original use case was to help improve elasticsearch_http performance.

elasticsearch_http blocks until the index request gets a response, so
simply doing more requests in-flight at any given time will improve
performance assuming processing or network-time is your bottleneck,
which in most cases it is.

In testing this, for 1,000,000 events, it took 150 seconds with 1
worker, 100 seconds with 2 workers, and 70 seconds with 4 workers. The
test was done on an EC2 m3.2xlarge logstash node writing to a two-node
elasticsearch 0.90.5 cluster on the same instance type (3 nodes total)
Merge pull request #708 from logstash/multiple-output-workers

Add 'workers' setting to output plugins.
Merge pull request #693 from bernd/LOGSTASH-1416

Use latest kibana for the flatjar. (LOGSTASH-1416)
Merge pull request #685 from bernd/fix-fail-invocation

Fix fail() invocation if no config file is given
Merge git://github.com/logstash/logstash