[SPARK-37099][SQL] Optimize the filter based on rank-like window function by reduce not required rows

[beliefer]

What changes were proposed in this pull request?

Sometimes, the filter condition compares rank-like(e.g. row_number, rank, dense_rank) window functions with number. For example,

SELECT *,
         ROW_NUMBER() OVER(PARTITION BY key ORDER BY a) AS rn
FROM Tab1
WHERE rn <= 5

We can extract the limit value 5 for window group and skip rows of window group in WindowExec.

In short, it supports following pattern:

SELECT (... (row_number|rank|dense_rank)()
    OVER (
PARTITION BY ...
ORDER BY  ... ) AS rn)
WHERE rn (==|<|<=) k
        AND other conditions

For these three rank-like functions (row_number|rank|dense_rank), the rank of a key computed on dataset always <= its total rows of whole dataset，so we can safely discard rows with rank > k, anywhere.

This PR also take over some functions from #34367.

Why are the changes needed?

Improve the performance.

Micro Benchmark
TPC-DS data size: 2TB.
This improvement is valid for tpcds q67 and no regression for other test cases.

TPC-DS Query	Default(Seconds)	After(Seconds)	Speedup(Percent)
q67	997.7585	882.8005	13.02%
All TPC-DS	7076.6715	6918.309	1.47%

Does this PR introduce any user-facing change?

'No'.
Just update the inner implementation.

How was this patch tested?

New tests.

[beliefer]

ping @zhengruifeng cc @cloud-fan

[cloud-fan]

I think it's overkill and very risky to make invasive changes to a fundamental physical operator like WindownExec. I like #34367 more which adds a new physical node. Can you elaborate on why is this better than #34367 ?

[beliefer]

I think it is OK to add a physical node, but the amount of code is a little large, and the filtering and reduction of data occur a little late.

[beliefer]

This PR has been replaced by #38799