[EPIC] Implement Range Partitioning

[gene-bordegaray]

Is your feature request related to a problem or challenge?

Partitioning::Range provides a way to represent range-partitioned physical layouts, but the optimizer and planning currently have guards that drop / reject this partitioning.

That is because the initial PR was purely mechanical, but follow-up work should preserve range partitioning where possible.

This will serve as a parent issue as more composable issues are made.

Describe the solution you'd like

Make physical optimizer and planning code range partitioning aware and preserve its metadata.

Some places to cover:

• Implement Range Repartitioning #22397
• Projection pushdown through RepartitionExec
• Sort pushdown through RepartitionExec
• Join output partitioning when one or both inputs are range partitioned
• Dynamic filter pushdowns / routing

Describe alternatives you've considered

None.

Additional context

Context: #21992