Implement user defined planner for extract

[xinlifoobar]

Which issue does this PR close?

Part of #11207 and closes #11220

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[jayzhan211]

👍

[alamb]

I merged this PR up from main to resolve some conflicts

[alamb]

Thanks again @xinlifoobar

[Omega359]

I just reset my branch with upstream main just now and I'm getting this in 4 of my tests:

---- network_time_parsing_should_work::case_2 stdout ----
Error: Result failed: Unable to transform sql expression 'extract(year FROM transaction_date)' to datafusion Expr: Some(NotImplemented("Extract not supported by UserDefinedExtensionPlanners: [Literal(Utf8(\"YEAR\")), Column(Column { relation: None, name: \"transaction_date\" })]"))

Is there some required changes to supporting code to facilitate the changes in this issue?

[Omega359]

Adding this clause to the plan_to_sql.rs:roundtrip_expr() test showcases the issue:

(
            TableReference::bare("person"),
            r#"extract(year from "2024-12-30"::date)"#,
            r#"fixme"#,
        ),

[Omega359]

The issue boils down to SqlToRel::new_with_options(..) not setting the planners. Unfortunately, I can't find a way to retrieve the list of planners set on the context to set them myself - I'll file a ticket for that shortly.

[alamb]

The issue boils down to SqlToRel::new_with_options(..) not setting the planners. Unfortunately, I can't find a way to retrieve the list of planners set on the context to set them myself - I'll file a ticket for that shortly.

issue / PR: #11296 / #11294