Feat: Make extract SQL expression timezone aware

[codetyri0n]

Which issue does this PR close?

• Closes Extract sql expression no longer is timezone aware #18228 .

Rationale for this change

This PR makes the extract expression timezone aware. The configuration of time zone (example - SET datafusion.execution.time_zone = '+04:00';) is now recognised and the extract statement correspondingly returns the right results through date_part.

What changes are included in this PR?

Are these changes tested?

Yes (slt)

Are there any user-facing changes?

Yes

[codetyri0n]

CC: @Omega359 @comphead

[Omega359]

I haven't had a chance to go over this in detail but can we add some tests to the .slt to test where the timestamp is being provided with a timezone? I didn't see any from a quick look.

[codetyri0n]

I haven't had a chance to go over this in detail but can we add some tests to the .slt to test where the timestamp is being provided with a timezone? I didn't see any from a quick look.

with the introduction of the tests recommended, it led to making extract independent from date_part --> it does not use the date_part udf. Lmk if you have any concerns.
Summarizing it here:

• date_part AND extract are now timezone config efficient
• extract is now registered as a separate datetime function
• corresponding changes made to mod.rs files and planner
• slt files and the test cases impacted have been modified accordingly (verified locally)

[Omega359]

I'll try and review this tomorrow though reading that extract was, err, extracted to a new function is a surprise.