adding nett4 dependency
new query.web subpackage and format QServer

the web server elements were spun out into classes a while ago, but
isolating them in a package is a bit cleaner
removing websockets from mqm

they are only used in the unfinished query2 project. may be
re-added later
WebSocketManager and QueryServlet moved + format

WSM moved from query to util. Didn't make any sense that it was in
query to start with since its primary use is for spawn2. QServlet
was moved to web
move async query shim logic into container class
factor out handler logic from server setup logic
moved some logging logic to QTracker

it was mostly used there anyway
pretty much working except qservlet and metrics

qservlet shouldn't be very hard to finish at this point. not sure
what im going to do about the metrics servlet. It doesn't use too
many of the http servlet request methods so a little dorky shim
might be fine
move servlet consumer and subclasses up

they were static and can encapsulate some logic from handleQuery
return of query call and metrics endpoint

basic functionality is present although error reporting is not as
helpful as of yet, compression has been temporarily disabled, and
some improvements can be made on handler integration and write
performance
license niceity for metrics servlet shim
don't write the table start twice for OutputHTML
report error cause for similar conditions as jetty

in the case where no bundles have been sent yet, error reporting
should be straight forward
move metrics servlet shim to util pkg
reduce logging levels and add handle interface

forgot to exclude interface change so ammending commit
remove some now unsed code in QServer

left some dead code related to logging for now to serve as a
reminder that that functionality is still missing
mqm as part of query call pipeline, outputs dry'd

mesh query master receives a query object and uses the pipeline
as the consumer. Right now this uses a bridge object but it doesn't
do much itself. This is steps to ward reducing query, handle, cancel,
source error, etc tangles.

the http output classes are more specialized to wards turning bundles
into strings and no longer implement data channel output nor concurrency
controls. (the concurrency will be handled by the pipeline, although in
practice I think it was previously handled by query op processor which was
kind of a mess)
minor: add override annotation
reduce logging levels on DCOtoNettyBridge

I cant help but feel that these commits represent a failure in to
have appropriately configurable logging
upgrade netty version