Fix for out-of-order support

Need to update "last written response" counter on the out-of-order path too, otherwise the channel eventually gets blocked after it has received lots of requests, thinking it hasn't written responses for any of them yet so it shouldn't keep taking more.
Add custom log pattern for nifty load tester
Skip writing responses if client disconnected while the request was running
Mark some of the nifty-examples deps as test-scoped only

This fixes some dependency checker errors which should up in incremental rebuilds of nifty, but don't show up in clean builds.
Add HTTP to ThriftTransportType enum
Move ChannelBuffer transports to core
Remove unnecessary close future handlers

When you add a channel to DefaultChannelGroup, netty already sets up a close future to remove the channel from the group when it is closed
Remove unused NettyThriftDecoder class
Add tests for ThriftFrameDecoder
Check for consistency of response ordering requirements across messages
Make netty's internal logger log to SLF4J in all nifty tests
Update facebook-oss-pom to v5 from v4
Remove leftover conflict markers
Add option to limit number of connections

Also, add test for this option
Fix 'mvn verify' warnings
[maven-release-plugin] prepare release nifty-parent-0.7.0
[maven-release-plugin] prepare for next development iteration
Shutdown channel factory if we created it
Fix test race condition

When finding an available port by binding a temporary ServerSocket to port 0, and then later using that port, the port might have been consumed by another test. Instead, tests should just bind the nifty server directly to port 0 and get the actual port it was bound to using getServerChannel after starting the server, and looking up the actual locally bound address.
Factor out more netty configuration specifics into the config builders

This change mainly adds control over number of boss and worker threads for the Netty channel factories used by the Netty client and server thread pools.

It also renames NettyConfigBuilder to NettyServerConfigBuilder (to contrast with NettyClientConfigBuilder), and turns the config builders into actual builders (they were just used directly before).