Add additional runs of columnPruningRules and WindowFilterPushDown

[xin-zhang2]

Description

1. SimplifyPlanWithEmptyInput might bring in new ProjectNodes. An additional run of columnPruningRules can be applied in case the child of the project is eligible for rewriting.
2. If the child is a WindowNode, an additional run of WindowFilterPushdown can be applied in case it can be replaced with RowNumber.
3. Also removed a redundant check in visitWindow of WindowFilterPushdown. The check is already performed in canOptimizeWindowFunction, and if the node doesn't meet the optimization criteria, the optimzation should be skipped rather than throwing an error.

Motivation and Context

Impact

Test Plan

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== NO RELEASE NOTE ==

[mohsaka]

Looks good to me. Seems like the only difference is an ordering change on the inner joins.

[hantangwangd]

@xin-zhang2 Thanks for this work. Is it possible to add a simple test case to show the effect of this change in somewhere like TestHiveLogicalPlanner?

[aditi-pandit]

@xin-zhang2 : Thanks for this change.

Its a bit odd that the join order changed in q58, especially since neither column pruning or window pushdown seems to have also caused a change of plans otherwise. Can you investigate further ?