Avoiding computation when window frame is always empty

Currently we allow constructs such as:

[ROWS | RANGE] between N FOLLOWING and M FOLLOWING

where N > M

These constructs always lead to an empty frame. We correctly return results of NULL or 0 values for sum/window functions, however we perform a lot of unneeded IO operations. We can optimise this away by looking at frame definitions before starting computation.