Create a server parameter that provides more fine-grained control than notablescan. Limit collection scans and full index scans to some constant. At planning time we can use the collection size to estimate this limit. In the presence of multi-key indexes we would not get a strict limit, but that's OK for the first implementation.

Note that this kind of reverts some of what was done in SPM-1024. However, the goal here is something more intelligent than maxScan and different than maxTimeMS – we want to reject queries before starting their execution (like notablescan).

Any attempt to do this should start by reviewing the findings of WRITING-33020.