Add table configuration option that limits the number of segments a single query may hit

This will limit the amount of compute wasted on a single query, protecting against queries that bog down the cluster.

This is especially necessary in the case of https://github.com/apache/incubator-pinot/issues/6187 as materializing all of those segments on disc is expensive.

The issue names no files, tests, or entry points; start by locating table configuration handling and the query path that selects segments. Clarify the configuration semantics and how the limit interacts with queries like issue 6187. Done means a table-level setting prevents one query from hitting more than the configured number of segments, with tests covering the behavior.

Written by the indexing model from the issue text.