Add the ability to limit query resource usage

from our community: Is there any way to set query RAM limits, timeouts, ... to prevent a too complex query endangering the entire instance?

Using this issue to start the discussion and planning of this type of capability.

- Ideally, they could be configured per org by an admin of the system.
- Initially, the 3 vectors could be limit by memory usage, by time, by number of results.
- Once queries trigger one of these limits, they would be cancelled and an error message returned to the user.

Start by reviewing the query execution and administration areas of InfluxDB; the issue names no files, tests, or entry points. Define how per-organization memory, time, and result-count limits would be configured, how cancellation works, and what error users receive before implementation.

Written by the indexing model from the issue text.