bug(expr): to_char prints wrong BC years

[xiangjinwu]

Describe the bug

ISO 8601 year 0 is display in PostgreSQL as 0001 BC instead of 0000. RisingWave fails to consider this in to_char.

Error message/log

dev=> select to_char('0001-01-01'::date - interval '1' second, 'YYYY');
 to_char 
---------
 0000
(1 row)

To Reproduce

select to_char('0001-01-01'::date - interval '1' second, 'YYYY');

Expected behavior

Same as PostgreSQL:

test=# select to_char('0001-01-01'::date - interval '1' second, 'YYYY');
 to_char 
---------
 0001
(1 row)

test=# select to_char('0001-01-01'::date - interval '1' second, 'YYYY BC');
 to_char 
---------
 0001 BC
(1 row)

test=# select to_char('0001-01-01'::date - interval '1' second, 'YYYY AD');
 to_char 
---------
 0001 BC
(1 row)

test=# select to_char('0001-01-01'::date + interval '1' second, 'YYYY BC');
 to_char 
---------
 0001 AD
(1 row)

test=# select to_char('0001-01-01'::date + interval '1' second, 'YYYY AD');
 to_char 
---------
 0001 AD
(1 row)

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

When using the chrono crate, although we can obtain the correct value with DateLike::year_ce instead of year, there is no corresponding specifier in its strftime module.

#11241 #15053