make HandlerUtils.readCf create and return a JsonArray of columns

While I was looking at something else, I noticed that the callers of
HandlerUtils.readCf both take the list of maps that gets populated, iterates
through the list, converts each map to a JsonObject, and then adds that object
to a JsonArray that is sent back in the response to the reply handler.

This commit removes that duplicate work and also eliminates the extra work of
looping over all of the columns again.
Merge pull request #116 from jsanda/refactor-readCf

make HandlerUtils.readCf create and return a JsonArray of columns
added counterhandler and coverage for such. closes #114
Added consistency handler and comments
Other handler related changes
Merge pull request #117 from zznate/counter-handler

added counterhandler and coverage for such. closes #114
Merge branch 'master' of https://github.com/zznate/intravert-ug into consistency_again

Conflicts:
	src/main/java/org/usergrid/vx/server/IntravertCassandraServer.java
Merge pull request #120 from zznate/consistency_again

Consistency again
adding back support for setting timeout per operation
Merge pull request #121 from jsanda/op-timeout

adding back support for setting timeout per operation
Make these piece reusable for testing
Some moves
Merge pull request #122 from zznate/morecleanup

Some moves
:) words to live by
Initialize in Server not in Handler.
Merge pull request #123 from zznate/morecleanup

Morecleanup
Its breaking
Merge pull request #125 from zznate/breakitall

Its breaking
wait until the entire response has been received to map the json
guard against NPEs

My previous changes to the readCf() method introduced some regressions around
the logic that determines how to calculate the column name and column value. I
needed to check if there is meta data for the column name and value. If and
only if there is meta data, the component value is calculated with a type
conversion; otherwise, we just take the raw byte buffer. Note that the
ByteBuffer cannot be stored as is in JsonObject. We need to get the bytes
which are in turn encoded. We might want to see about providing an alternate
implementation that will be more efficient, if that is possible.