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)