[MINOR] Fix flaky test testDeletePartitionsV2

[yihua]

Change Logs

This PR fixes the flaky test testDeletePartitionsV2 as shown below. The root cause is that the test expects 3 partitions to be written by deletePartitionSetup but the random record generator can generate records in fewer partitions due to how the partition path value is set.

https://github.com/apache/hudi/actions/runs/14589199410/job/40920578922

Error:  Tests run: 57, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 172.08 s <<< FAILURE! - in org.apache.hudi.TestHoodieSparkSqlWriter
Error:  testDeletePartitionsV2{boolean}[2]  Time elapsed: 3.315 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <6> but was: <4>
	at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
	at org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:62)
	at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
	at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
	at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
	at org.apache.hudi.TestHoodieSparkSqlWriter.validateDataAndPartitionStats(TestHoodieSparkSqlWriter.scala:902)
	at org.apache.hudi.TestHoodieSparkSqlWriter.testDeletePartitionsV2(TestHoodieSparkSqlWriter.scala:859)

Impact

Fixes the test flakiness and makes CI stable

Risk level

none

Documentation Update

none

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[hudi-bot]

CI report:

• 1da10cd Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build