Flaky Test: WriteAndReadMetricsTest#test

### Code of Conduct

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

### Search before asking

- [X] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues.

### Describe the flaky test

```
Error: Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 20.532 s <<< FAILURE! - in org.apache.uniffle.test.WriteAndReadMetricsTest
Error: test Time elapsed: 17.767 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <55> but was: <51>
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:182)
at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)
at org.apache.uniffle.test.SparkIntegrationTestBase.verifyTestResult(SparkIntegrationTestBase.java:116)
at org.apache.uniffle.test.SparkIntegrationTestBase.run(SparkIntegrationTestBase.java:63)
at org.apache.uniffle.test.WriteAndReadMetricsTest.test(WriteAndReadMetricsTest.java:39)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
```

### Actions URL

1. https://github.com/apache/incubator-uniffle/actions/runs/3681962312/jobs/6229151235
2. https://github.com/apache/incubator-uniffle/actions/runs/4081935743/jobs/7035772792

### Parent issue

#1733

### Are you willing to submit PR?

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

Start by running WriteAndReadMetricsTest#test and read test/integration code around WriteAndReadMetricsTest.java:39 and SparkIntegrationTestBase.java:63,116. Compare the reported expected 55 versus actual 51 result and the linked action runs to identify why the test is nondeterministic. Done means the test passes reliably with a justified result across repeated runs.

Written by the indexing model from the issue text.