[SPARK-53318][SQL] Support the time type by make_timestamp_ltz()

[uros-db]

What changes were proposed in this pull request?

In the PR, I propose to extend the make_timestamp_ltz function, and accept a date and time fields.

Syntax

make_timestamp_ltz(date[, time])

Arguments

• date: A date expression.
• time: A time expression.

Returns
A TIMESTAMP_LTZ.

Examples

> SELECT make_timestamp_ltz(DATE'2014-12-28', TIME'6:30:45.887');
 2014-12-28 06:30:45.887

Why are the changes needed?

Users will be able to create a timestamp with local time zone by combining a time and a date.

Does this PR introduce any user-facing change?

Yes, this extends make_timestamp_ltz to accept additional kinds of inputs.

How was this patch tested?

Added new e2e SQL tests in corresponding golden files.

Was this patch authored or co-authored using generative AI tooling?

No.

[jcw024]

Can we also update the examples with the new usage?

examples = """
Examples:
SELECT FUNC(2014, 12, 28, 6, 30, 45.887);
2014-12-28 06:30:45.887
SELECT FUNC(2014, 12, 28, 6, 30, 45.887, 'CET');
2014-12-27 21:30:45.887
SELECT FUNC(2019, 6, 30, 23, 59, 60);
2019-07-01 00:00:00
SELECT FUNC(null, 7, 22, 15, 30, 0);
NULL
""",

[uros-db]

Can we also update the examples with the new usage?

Sure! Added two new expression examples.

[jcw024]

Thanks for making the updates. Just a couple last suggestions, can we also update the arguments to include date similar to how it's done in the other MakeTimestamp ExpressionBuilders?

  * date - a date to represent, from 0001-01-01 to 9999-12-31

Also, I'm wondering if we should also apply similar changes to TryMakeTimestampLTZExpressionBuilder. I think it would make sense to also go in this PR since the change is so similar, but I'm not sure how it was done for the other TryMakeTimestamp ExpressionBuilders

[uros-db]

@jcw024 Arguments updated accordingy. As for try_make_timestamp_ltz - please see: #52063.

[jcw024]

changes LGTM!

[uros-db]

@cloud-fan Please review.

[cloud-fan]

thanks, merging to master!