feat(query): timestamp type can modify output format with new setting TIMESTAMP_OUTPUT_FORMAT

[TCeason]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

timestamp type can modify output format with new setting TIMESTAMP_OUTPUT_FORMAT

About new setting

+-------------------------+-------------------------+-------------------------+----------------------------------------------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------+--------+
| name                    | value                   | default                 | range                                              | level   | description                                                                                                                                   | type   |
+-------------------------+-------------------------+-------------------------+----------------------------------------------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------+--------+
| timestamp_output_format | '%Y-%m-%d %H:%M:%S%.6f' | '%Y-%m-%d %H:%M:%S%.6f' | ["%Y-%m-%d %H:%M:%S%.3f", "%Y-%m-%d %H:%M:%S%.6f"] | SESSION | Specifies the display format for the TIMESTAMP data type alias. Available values include '%Y-%m-%d %H:%M:%S%.6f' and '%Y-%m-%d %H:%M:%S%.3f'. | String |
+-------------------------+-------------------------+-------------------------+----------------------------------------------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------+--------+

Fixes #14169

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[TCeason]

Maybe we can remove this impl in this pr?

https://github.com/datafuselabs/databend/blob/aa97d2c5b57f1585abc8192e5fb76f9fc4157903/src/query/datavalues/src/types/type_timestamp.rs#L37

cc @andylokandy

[github-actions]

Docker Image for PR

• tag: pr-14174-bb779e3

note: this image tag is only available for internal use,
please check the internal doc for more details.

[youngsofun]

date/timestamp format should be part of file formats, not a setting.

1. this is naturally part of a format spec, it should be stable.
2. we do not hope users to rely on settings, most used internally (affect how we run it, but not the results).
3. during a session, mutli diff date/timestamp formats may be involved

[TCeason]

date/timestamp format should be part of file formats, not a setting.

1. this is naturally part of a format spec, it should be stable.
2. we do not hope users to rely on settings, most used internally (affect how we run it, but not the results).
3. during a session, mutli diff date/timestamp formats may be involved

1. in this issue: Feature: Databend needs to distinguish between DateTime and Timestamp #14169 we need support format.
2. sf does the same things. https://docs.snowflake.com/en/sql-reference/data-types-datetime#date-and-time-formats

[youngsofun]

date/timestamp format should be part of file formats, not a setting.

1. this is naturally part of a format spec, it should be stable.
2. we do not hope users to rely on settings, most used internally (affect how we run it, but not the results).
3. during a session, mutli diff date/timestamp formats may be involved

1. in this issue: Feature: Databend needs to distinguish between DateTime and Timestamp #14169 we need support format.
2. sf does the same things. https://docs.snowflake.com/en/sql-reference/data-types-datetime#date-and-time-formats

yes, like sf, we should distinguish query output and format output, it is ok for settings to only affect the former.
https://docs.snowflake.com/en/sql-reference/date-time-input-output#label-date-time-input-output-how-snowflake-determines
I think most of the time query output is interpreted to Date/TS type for PY/JAVA/.., instead of used directly, so the ts format for query output is not needed, it is only for transformation and presentation.

[BohuTANG]

@youngsofun Yes, I think this is mainly for the third-party SaaS intergration. But now we can not say the superset side issue related to this timestamp format, @hantmac are still investigating.

[andylokandy]

To avoid uninitialized function context:

Suggested change

	// 1. If write a wrong format, .format(ts_format) will display the ts_format directly.
	debug_assert!(!ts_format.trim().is_empty());
	// 1. If write a wrong format, .format(ts_format) will display the ts_format directly.

[BohuTANG]

Confirmed, there is no need add this setting, let's close this PR, thanks all.