perf(over window): pass through Updates not affecting window function outputs

[stdrc]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

If an incoming Update only changes fields other than partition key, order key and window function arguments, the win func outputs should stay the same. This PR eliminates the redundant re-computation for such kind of Updates.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[stdrc]

• perf(over window): skip remaining affected rows when rank is not changed #18950
• perf(over window): pass through Updates not affecting window function outputs #19056 👈
• perf(over window): avoid recompute information about window frames #19036
• fix(over window): fix table iter pk prefix to use deduped partition key #19081
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @stdrc and the rest of your teammates on Graphite

[xxchan]

I can now understand if the result of the func call is persisted, this optimization makes sense (sth like MaterializedProject will be similar), but I'm not familiar with the previous impl of OverWindow and why we persisted the func calls here.

Also code is not reviewed, but loc looks good.

So rubber stamp