Streaming query client

This pops up as a requirement when quickstart join query might generates many rows. It may blow up broker memory as it tries to keep all the rows in memory then return it back.

The goal of this PR is to provide a grpc based query client. And we can also use it to replace controller console.

This client should config a timeout for broker so it won't hold the resources on server side.

cc: @walterddr

Start by tracing the quickstart join query and the controller console query path to understand how rows are currently returned and where broker resources are held. Then review the proposed gRPC query client and timeout requirements. Done means the scope and interface are defined, large results can be streamed without retaining all rows in broker memory, and broker-side resources are bounded by a timeout.

Written by the indexing model from the issue text.