Fix memory leak in syslog input. (tcp server)

Remove the client from the clients list when the connection is closed.
since the plugin's name changed to collate, update the comments and method name, vars to collate, to keep consistent
working kafka input
fixed looping issue eating up cpu
cleaned up shutdown to flush log queues.
updated client to make it more fault tolerant
Pathing has changed within the kibana project.

pathing to the dashboards has changed.
(cherry picked from commit f8e1f6a)
Use latest kibana for the flatjar. (LOGSTASH-1416)
(cherry picked from commit 79d1863)
Upgrade jruby
(cherry picked from commit af05119)
Update JRuby auto-installer in bin/logstash to use JRuby 1.7.5
(cherry picked from commit 733b2bb)
Updated JRuby URL for downloading 1.7.5
(cherry picked from commit 60064f7)
- remove old junk
(cherry picked from commit a4a0a21)
fixed shutdown issues
Break out json into json_lines so that users streaming json can use the line delimited codec and users using message based transports i.e. redis can still use a codec without requiring the message end in '\n'
Add more descriptive docs for json/json_lines codecs
Allow output plugins to declare that, for a given configuration, workers are
not supported. Such reasons could include inability to share a resource
(like a listening socket, etc). This declaration will force a
single-worker setting and allow logstash to warn the user instead of
aborting.
Try to fix any @timestamp values if someone mucks with that field value
and turns it into a string through the json filter.
purge old and long-since-deprecated amqp plugins
- Include a (hopefully) better warning message when using an output
plugin that doesn't support workers.
- Remove worker_setup_skip hackery; not needed.
- update file and zeromq workers_not_supported settings