SPARK-1729. Make Flume pull data from source, rather than the current pu...

...sh model

Currently Spark uses Flume's internal Avro Protocol to ingest data from Flume. If the executor running the
receiver fails, it currently has to be restarted on the same node to be able to receive data.

This commit adds a new Sink which can be deployed to a Flume agent. This sink can be polled by a new
DStream that is also included in this commit. This model ensures that data can be pulled into Spark from
Flume even if the receiver is restarted on a new node. This also allows the receiver to receive data on
multiple threads for better performance.
Actually if the transaction returns null, eventBatch will remain ErrorEventBatch or None - if that change is made (from the initial assignment) which leads to a FlumeException - which will be caught by Avro IPC and a corresponding exception thrown on the other side(streaming side), which we catch and log.(Avro IPC guarantees this)