feat: support reverse scan for hummock

[Little-Wallace]

Is your feature request related to a problem? Please describe.

In past scenes, we only need forward scan in all of state executor. So we remove backward scan of hummock because it is hard to implement reverse iterator of delete-range.

@st1page propose a expanded range cache to store part of keys in memory. Sometimes we may need to load more data from hummock, and if we want to load data from the left side of cache, we need to a reverse-scan.

Describe the solution you'd like

The interface shall support range bound and item limit.

Describe alternatives you've considered

Maybe I need some time to think of how to implement reverse iterator of delete range.

Additional context

No response

[st1page]

c.c. @stdrc

[fuyufjh]

#12570

[hzxa21]

This can be simplified with #13148

[hzxa21]

#13148 is done. I think we can continue to support reverse scan based on vnode watermark. @Little-Wallace @wenym1

[fuyufjh]

Ping. Over-window function is still waiting for this.

[hzxa21]

Done in #12570