feat(expr): support interval to_char()

[KeXiangWang]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

To solve #13561
Postgres' corresponding doc here.

In Postgres, an interval is first converted to a timestamp, and then use timestamp's to_char() implementation to convert the interval to a char. But chrono doesn't support interval type, especially negative intervals.
To reuse the format parsing implementation of chrono, in this PR, we still first convert the template to chrono template, and then format the interval based on the the Item types and the corresponding behaviors in Postgres.

In the test file, you may see some output really wired. For example,

select to_char('-120hours'::interval, 'HH12');
----
012

I have to say the implementation of postgres is not prudent and unified among different Items. Here, I choose to strictly follow their behaviors.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

to_char

Converts the input to string according to the given format. Both uppercase and lowercase formats are supported.

to_char ( timestamptz, format ) → *string*
to_char ( timestamp, format ) → *string*
to_char ( interval, format ) → *string*

to_char(timestamp '2002-04-20 17:31:12.66', 'HH12:MI:SS') → '05:31:12'

to_char('2023-07-11 20:01:00-07:00'::timestamptz, 'HH12:MI:SS TZH:TZM') → 03:01:00 +00:00

to_char('1year 2 month 3day 4hour 5minute 6second'::interval, 'YYYY MM DD PM HH12 HH24 MI SS MS US') → 0001 02 03 AM 04 04 05 06 000 000000

[codecov]

Codecov Report

Attention: 192 lines in your changes are missing coverage. Please review.

Comparison is base (640befd) 67.99% compared to head (78f584b) 67.88%.

Files	Patch %	Lines
src/expr/impl/src/scalar/to_char.rs	5.88%	192 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14071      +/-   ##
==========================================
- Coverage   67.99%   67.88%   -0.11%     
==========================================
  Files        1554     1554              
  Lines      268874   269076     +202     
==========================================
- Hits       182819   182670     -149     
- Misses      86055    86406     +351     

Flag	Coverage Δ
rust	67.88% <5.88%> (-0.11%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[xxchan]

Is there any pg regress tests for it? 🤔

[KeXiangWang]

Is there any pg regress tests for it? 🤔

Good point! will check.

[wangrunji0408]

LGTM for the code. I don't check the format.

[TennyZhuang]

Generally LGTM

[KeXiangWang]

Is there any pg regress tests for it? 🤔

Unfortunately, no available regress tests for us, the tests are either for timestamp and timestamptz or composed of currently unsupported patterns.