[Bug] Time-Zone problems in TimeRangeIteratorTest

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Version

1.3.2-SNAPSHOT

### Describe the bug and provide the minimal reproduce step

The TimeRangeIteratorTest.testNaturalMonthTimeRange test is failing for me, as I am currently in a timezone Berlin/Europe which currently (16.05.2024) is at daylight-saving and hereby has a time offset of 2h and not 1h.

### What did you expect to see?

I expected the test to pass

### What did you see instead?

The test failed.

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Start with TimeRangeIteratorTest.testNaturalMonthTimeRange and reproduce the failure using the Europe/Berlin timezone described in the issue. Trace the test's expected time range around daylight-saving time, then verify that the test passes without depending on a one-hour offset.

Written by the indexing model from the issue text.