FluxDB consumable in streaming + specifying boundaries

[abourget]

There's a few things that would be desired:

• [ ] GraphQL exposure, in streaming
• [ ] Implement lower_bound, to continue when things drop

The current JSON is streaming from a server's perspective, but because it arrives as a list, it would require some funky streaming-JSON reader on the client. Otherwise, it needs to be buffered.

FluxDB has no problem streaming out 10 GB, but the client might not be in that situation. A GraphQL streaming snapshot would allow the consumer to handle disconnections, and using the lower_bound, continue where it left off, alongside the capacity to not buffer the whole response.