Add protections to limit the impact of rogue queries

When a rogue query does an expensive/resource intensive operations (full table scan on a very large table), it may consume more resources and affect the health of the servers (out of memory, high cpu etc). The effects are more pronounced when multiple bad queries land around the same time window.

We could add some protection at table level to limit the max segments (count / %) scanned per query.