fix(over window): fix over window range cache shortcut return

[stdrc]

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

What's changed and what's your intention?

Previously the extend_cache_by_range(self, table, range: RangeInclusive<&StateKey>) method wrongly shortcut returned after loading the left half of range, pseudo-code like below:

if left_extendable && range.start < first_key_in_cache {
  return extend_cache_by_range_inner(Range(Include(range.start), Exclude(first_key_in_cache)));
}

if right_extendable && range.end > last_key_in_cache {
  return extend_cache_by_range_inner(Range(Exclude(last_key_in_cache), Include(range.end)));
}

But it actually should be:

if left_extendable && range.start < first_key_in_cache {
  extend_cache_by_range_inner(Range(Include(range.start), Exclude(first_key_in_cache)));
}

if right_extendable && range.end > last_key_in_cache {
  extend_cache_by_range_inner(Range(Exclude(last_key_in_cache), Include(range.end)));
}

This PR correct it and re-enable e2e tests for range cache.

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.