Flaky tests in DurableTasks

## Expected Behavior Currently this test is causing issues in our pipelines. ## Actual Behavior Flaky: ``` Error: Tests run: 42, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 125.0 s <<< FAILURE! -- in io.dapr.durabletask.DurableTaskClientIT Error: io.dapr.durabletask.DurableTaskClientIT.loopWithTimer -- Time elapsed: 7.542 s <<< FAILURE! org.opentest4j.AssertionFailedError: expected: <2> but was: <-58> at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151) at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132) at org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197) 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:531) at io.dapr.durabletask.DurableTaskClientIT.loopWithTimer(DurableTaskClientIT.java:175) at java.base/java.lang.reflect.Method.invoke(Method.java:569) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) [INFO] [INFO] Results: [INFO] Error: Failures: Error: DurableTaskClientIT.loopWithTimer:175 expected: <2> but was: <-58> ``` ## Steps to Reproduce the Problem <!-- How can a maintainer reproduce this issue (be detailed) --> ## Release Note <!-- How should the fix for this issue be communicated in our release notes? It can be populated later. --> <!-- Keep it as a single line. Examples: --> <!-- RELEASE NOTE: **ADD** New feature in Dapr. --> <!-- RELEASE NOTE: **FIX** Bug in runtime. --> <!-- RELEASE NOTE: **UPDATE** Runtime dependency. --> RELEASE NOTE: