[pipeline-connector][mysql] fix timestamp with timezone format

[whhe]

Try to fix #2950

[Jiabao-Sun]

Thanks @whhe for this contribution. It makes sense.
I'm a little curious why this question only appears in MySQL8.
By the way, could you please add some tests in MySqlFullTypesITCase ?

[bingxindan]

On which version will this bug be fixed? I will download one and test it out

[whhe]

Thanks @whhe for this contribution. It makes sense. I'm a little curious why this question only appears in MySQL8. By the way, could you please add some tests in MySqlFullTypesITCase ?

Sure, I will have a try to add a full types test case for it soon.

For the issue cause, now the pipeline connector converts TIMESTAMP to TIMESTAMP_LTZ in MySqlTypeUtils.java#L194, while the original mysql source connector does not deal with TIMESTAMP WITH TIME ZONE, so it I think should only occur in e2e case.

[Jiabao-Sun]

Thanks @whhe for this contribution. It makes sense. I'm a little curious why this question only appears in MySQL8. By the way, could you please add some tests in MySqlFullTypesITCase ?

Sure, I will have a try to add a full types test case for it soon.

For the issue cause, now the pipeline connector converts TIMESTAMP to TIMESTAMP_LTZ in MySqlTypeUtils.java#L194, while the original mysql source connector does not deal with TIMESTAMP WITH TIME ZONE, so it I think should only occur in e2e case.

Thanks @whhe.

https://github.com/ververica/flink-cdc-connectors/blob/1b643026fe93ed477541dcd7e97001785840a296/flink-cdc-connect/flink-cdc-pipeline-connectors/flink-cdc-pipeline-connector-mysql/src/test/resources/ddl/column_type_test_mysql8.sql#L108

Change it to timestamp_c TIMESTAMP(0) NULL DEFAULT '2000-01-01 00:00:00' can reproduce this problem.

[whhe]

Because MySqlValueConverters always uses UTC, so using Instant.parse is OK for other cases, here I only changed the parsing related to default value.

[Jiabao-Sun]

LGTM