Create a more idiomatic Finagle setup

The previous version was effectively serializing all incoming requests by doing all work on on the event loop. This patch provides a setup closer to what one might see in production code.

The serialization benchmark ships serialization off to a thread pool. Previously work was being done on the event loop and the result was sent to the pool.

We have a (still experimental) mysql client built on finagle that we're using for the db benchmarks. This ensures the bottleneck is never how the jdbc adapter is tuned. Also the previous setup was doing all queries on the event loop and providing the result. This patch provides true parallelization of queries.

Finally we have jackson emit byte arrays and use wrapped buffers instead of copied buffers to avoid the extra work of copying.