Fix flaky TestHoodieJavaClientOnCopyOnWriteStorage

TestHoodieJavaClientOnCopyOnWriteStorage could nondeterministically stop the JVM to shutdown, which causes the some CI modules to timeout. 

How to reproduce: run the following commands 10+ times to find it would block the terminal.
{code:java}
mvn clean -Dscala-2.12 -Dspark3.2  install -DskipTests -T 2C -am

mvn test -Punit-tests -fae -Dspark3.2 -Dscala-2.12 -pl hudi-client/hudi-java-client  -e -ntp -B -V -Dgpg.skip -Djacoco.skip -Pwarn-log -Dorg.slf4j.simpleLogger.log.org.apache.maven.plugins.shade=warn -Dorg.slf4j.simpleLogger.log.org.apache.maven.plugins.dependency=warn -Dmaven.wagon.httpconnectionManager.ttlSeconds=25 -Dmaven.wagon.http.retryHandler.count=5 -Dtest=TestHoodieJavaClientOnCopyOnWriteStorage{code}

## JIRA info

- Link: https://issues.apache.org/jira/browse/HUDI-7328
- Type: Bug
- Epic: https://issues.apache.org/jira/browse/HUDI-4302

Start with TestHoodieJavaClientOnCopyOnWriteStorage in hudi-client/hudi-java-client and run the supplied Maven test command repeatedly, after the build command. Trace why the test can stop the JVM and leave the terminal or CI module blocked. Done means repeated runs complete reliably without JVM shutdown or module timeouts.

Written by the indexing model from the issue text.