Temporarily fix date format failed cases for non-UTC time zone.

[res-life]

Related to #10083

When time zone is non-UTC, formating timestamp column which contains 9999-12-31 time will do the following:

• step1: rebase from microseconds of 9999-12-31 to the microseconds of 10000-01-01 according to non-UTC tz.
• step2: use cuDF to format 10000 years to get the strings.
  In the above step 2, cuDF has limitation, it truncate 10000 to 0000
  Refer to link, cuDF supports %Y has a 4 digits length.

specifier_map specifiers = {
    {'Y', 4}, {'y', 2}, {'m', 2}, {'d', 2}, {'H', 2}, {'I', 2}, {'M', 2},

// will truncate `10000` to `0000`
cv.asStrings("%Y-%m-%d")

This PR is a workaround to temporarily fix this issue.
After we have a new kernel to handle Java time format, we then revert this PR.

Signed-off-by: Chong Gao res_life@163.com

[res-life]

build