perf(over window): locality-based range cache for general over window executor

[stdrc]

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

What's changed and what's your intention?

This PR implements a range cache for general OverWindowExecutor. Instead of retaining everything in an accessed over partition in memory, the range cache only caches recently accessed range of rows in each accessed partition. This can significantly reduce memory footprint for window function calls with bounded window frames like lead(x) over (...), sum(x) over (partition by ... order by ... rows 10 preceding).

This fixes #11502.

A session variable called RW_STREAMING_OVER_WINDOW_CACHE_POLICY is introduced to control the cache policy:

• full: default policy, cache all entries in each accessed partition, just like before
• recent: cache only recently accessed range
• recent_first_n: cache only the first several entries in recently accessed range
• recent_last_n: cache only the last several entries in recently accessed range

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• [ ] 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 contains user-facing changes.

Click here for Documentation

Types of user-facing changes

Please keep the types that apply to your changes, and remove the others.

• Installation and deployment
• Connector (sources & sinks)
• SQL commands, functions, and operators
• RisingWave cluster configuration changes
• Other (please specify in the release note below)

Release note

[stdrc]

The workflow requires members of Cargo.lock team to approve because there's one change in Cargo.lock file. Plz help take a look @BugenZhao @TennyZhuang @wangrunji0408