[FLINK-37306][tests] Fix MySQLSourceITCase failure in non-UTC timezone

[yuxiqian]

This closes FLINK-37306.

The failing test cases were introduced in #3298 and #3876 (and more), but has not been exposed until we decided to run CI test cases in random timezones (#3650).

MySQLSourceITCase#testSourceMetrics

MySQL docker container runs in UTC timezone by default, but MySQLSourceITCase#testSourceMetrics didn't specify serverTimeZone option explicitly like other test cases. As a result, running test cases in non-UTC timezone will fail with the following error:

org.apache.flink.table.api.ValidationException: The MySQL server has a timezone offset (0 seconds ahead of UTC) which does not match the configured timezone GMT+XX:XX. Specify the right server-time-zone to avoid inconsistencies for time-related fields.

MySqlTimezoneITCase, MysqlDebeziumTimeConverterITCase, and SpecificStartingOffsetITCase

These cases need to run MySQL container in specific timezones, so they all have a method called buildMySqlConfigWithTimezone to create MySQL container with the same timezone as JVM.

However, JVM timezone (fetched via ZoneId.systemDefault()) returns UTC-offset timezone in GMT+04:30 format, while MySQL configuration file requires it in +04:30 format. This would block the container from starting up.

MySqlMultipleTablesRenamingITCase

This test case uses the same time-zone initialization code as MySqlTimezoneITCase. Removed these codes and stick to UTC considering this case is not time-zone sensitive.

[yuxiqian]

@leonardBang @lvyanquan PTAL

[leonardBang]

https://issues.apache.org/jira/browse/FLINK-37306 Could you link to this ticket ?

[leonardBang]

+1