[Bug] [doris] doris2.1 datetimev2 issue

### Search before asking

- [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues.

### What happened

doris 2.1.8 to doris 2.1.10
datetimev2 synchronised after the date becomes 1970-01-21

### SeaTunnel Version

2.3.11

### SeaTunnel Config

```conf
env {
parallelism = 1
job.mode = "STREAMING"
checkpoint.interval = 5000
}
source {
Doris {
fenodes = "x.x.x.x:8030"
username = "root"
password = "***"
database = "test"
table = "d_event"
}
}

sink {
Doris {
fenodes = "x.x.x.x:8030"
username = "root"
password = "****"
database = "test"
table = "d_event"
sink.label-prefix = "test-cdc"
sink.enable-2pc = "true"
sink.enable-delete = "true"
sink.max-retries = 3
doris.config = {
format = "json"
read_json_by_line="true"
}
}
}
```

### Running Command

```shell
./bin/seatunnel.sh --config ./job/doris.conf -m local
```

### Error Exception

```log
none
```

### Zeta or Flink or Spark Version

_No response_

### Java or Scala Version

jdk8

### Screenshots

doris 2.1.8
datetimev2 synchronised after the date becomes 1970-01-21

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

Start by reproducing the datetimev2 synchronization with Doris 2.1.8 and 2.1.10 using the provided SeaTunnel 2.3.11 configuration and local-mode command. Compare the source and sink datetime values and trace the Doris connector's datetime handling; done means identifying and correcting the conversion that produces dates near 1970-01-21, with a regression test covering the case.

Written by the indexing model from the issue text.