consider date_bin in range partition satisfaction

[jayshrivastava]

Which issue does this PR close?

• Related to Support functions date_bin and date_trunc in range partition satisfaction #23569.

Rationale for this change

When a projection calls date_bin on a column used in a Partitioning::Range expression, the projection should preserve the Partitioning. This enables the optimizer to use the partitioning property in later plan nodes.

Example 1

ordering = [timestamp ASC]

  split points = [
      (2024-01-01 10:00),
      (2024-01-01 11:00),
  ]

Projecting date_bin(15 minutes, 10:00) as time_bin allows us to safely preserve the partitioning on the new expression:

ordering = [time_bin ASC]

  split points = [
      (2024-01-01 10:00),
      (2024-01-01 11:00),
  ]

This can be done without repartitioning as long as the date_bin "widow" does not cross any split points and is smaller than all of the ranges. For example, these would not work in this scenario:

• date_bin(16 minutes, 10:00) as time_bin
• date_bin(2 hours, 10:00) as time_bin

When the range partitioning tuple expression is on multiple columns, we fallback to the current behavior, using UnknownPartitioning.

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[jayshrivastava]

Closed in favor of #24501 (review)