index intersection needs to track memory usage and abort if it's too high

Should do this in a fashion similar to how sort does it. Unclear if we want to use the incorrect accounting that sort currently uses or the 'real' accounting that is much leaner. Either way, we should do something.

All of the logic to fall back on an indexed sort should be generalized to fall back on a non-blocking plan.