[Fix][e2e] Fix flaky Redis tests

[dybyte]

Purpose of this pull request

This PR fixes flaky Redis tests.

2025-10-30T21:33:29.1934764Z [ERROR] Failures: 
2025-10-30T21:33:29.1935455Z [ERROR]   RedisClusterIT.testRedisClusterCustomValueWithListType:349 expected: <100> but was: <132>
2025-10-30T21:33:29.1937019Z [ERROR]   RedisClusterIT.testRedisClusterCustomValueWithListType:349 expected: <100> but was: <132>
2025-10-30T21:33:29.1938065Z [ERROR]   RedisClusterIT.testRedisClusterCustomValueWithListType:349 expected: <100> but was: <132>
2025-10-30T21:33:29.1939086Z [ERROR]   RedisClusterIT.testRedisClusterCustomValueWithListType:349 expected: <100> but was: <132>
2025-10-30T21:33:29.1940211Z [ERROR]   RedisClusterIT.testRedisClusterCustomValueWithListType:349 expected: <100> but was: <132>
2025-10-30T21:33:29.1941290Z [ERROR]   RedisClusterIT.testRedisClusterCustomValueWithListType:349 expected: <100> but was: <132>
2025-10-30T21:33:29.1942187Z [ERROR]   RedisClusterIT.testRedisClusterScan:294 expected: <100> but was: <132>
2025-10-30T21:33:29.1943049Z [ERROR]   RedisClusterIT.testRedisClusterScan:294 expected: <100> but was: <132>
2025-10-30T21:33:29.1943823Z [ERROR]   RedisClusterIT.testRedisClusterScan:294 expected: <100> but was: <132>
2025-10-30T21:33:29.1944866Z [ERROR]   RedisClusterIT.testRedisClusterScan:294 expected: <100> but was: <132>
2025-10-30T21:33:29.1945655Z [ERROR]   RedisClusterIT.testRedisClusterScan:294 expected: <100> but was: <132>
2025-10-30T21:33:29.1946415Z [ERROR]   RedisClusterIT.testRedisClusterScan:294 expected: <100> but was: <132>

The RedisClusterIT test class involves multiple Redis clusters, which can lead to race conditions in the sink, resulting in duplicate writes.
Given that the batch size is 33, a total of 33 × 4 = 132 records can occasionally appear due to this race condition.
To address this, I modified some test cases that handle the List type.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Covered by existing tests.

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config

[chl-wxp]

Thank you very much, I also encountered this problem

[chl-wxp]

LGTM

[davidzollo]

+1