Some bugs when TiCDC setting the timezone

[hi-rustin]

What did you do?

Set the timezone to TiCDC server and sink-uri. How does TiCDC set the time zone internally?

What did you expect to see?

TiCDC uses timezone correctly.

What did you see instead?

1. We unescape the timezone value twice.
2. We use the wrong ctx when we get the timezone.
3. We should not suggest users use CST to create the changefeed in docs.
4. We should not suggest users use time-zone="" in sink-uri.
5. Should we only keep the time-zone from the sink-uri? Considering multi-tenancy, we should not use server configurations.
6. TiCDC can not handle the timezone for some DDLs correctly. We need to add docs for it.

Versions of the cluster

TiCDC version (execute cdc version):

v6.5.1

[nongfushanquan]

/close

[ti-chi-bot]

@nongfushanquan: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.