Move `sql_compound_identifier_to_expr` to `ExprPlanner`

[alamb]

Is your feature request related to a problem or challenge?

Part of #11207

As discussed in #11207 The idea is to move hardcoded the sql_compound_identifier_to_expr operator to function in the parser step, which is currently handled in the optimizer step. We need to implement user-defined parser mechanisms to enable more flexible SQL planning.

Describe the solution you'd like

No response

Describe alternatives you've considered

I think you can just follow the model of #11398 and add a function to ExprPlanner and then update the sql planner to call it instead of get_functon_meta

Additional context

No response

[dharanad]

seems like a duplicate of #11244
i will close and we can keep this open

[dharanad]

take

[alamb]

Sorry @dharanad -- I didn't see #11244 before

[dharanad]

Sorry @dharanad -- I didn't see #11244 before

No worries at all.

[dharanad]

QQ: @alamb In sql_compound_identifier_to_expr the only this which is using get_function_meta is get_field ScalarUDF. I think ideally we should move get_field to ExprPlanner. Rest of code as dependecy on SqlToRel struct

[alamb]

I think ideally we should move get_field to ExprPlanner. Rest of code as dependecy on SqlToRel struct

Makes sense to me 👍

[alamb]

After #11487 I wonder if there is anythng left for this item?

[jayzhan211]

I think we are done with this item