Add Serialization + Persistence JMH Benchmark

@colinsurprenant @jakelandis @suyograo @jordansissel

As discussed we should have a serialization + subsequent disk write benchmark suit.

The way I suggest setting this up is:

* Create a few `M` events on heap and in an `Event[]` array (we shouldn't have any overhead from storing these, the more we can get on heap and actually run through in the benchmark itself, the better => array imo, we can do multiple arrays if we want to run multiple threads for input to the Queue)
* Try to use events of realistic size and "shape". Our Apache log dataset seems like a good bet here.

This is basically just an extension of `org.logstash.benchmark.QueueWriteBenchmark` that runs off of an array of events :)