KAFKA-19286: Fix flaky testConcurrentRemoveReadForCache1

[UladzislauBlok]

Fix for flaky testConcurrentRemoveReadForCache1

Short description of root cause:

Before scheduler starts clean up, he's triggering read thread. If it's
happening before RemoteIndexCache#remove does remove entity from cache,
reader thread will successfully read entity, and won't trigger fetching
from remote log

Full analysis:

https://issues.apache.org/jira/browse/KAFKA-19286

Evidence:

Run entire test class and annotate testConcurrentRemoveReadForCache1 as
RepeatedTest to run 100_000 times

Result:

./gradlew storage:test --tests org.apache.kafka.storage.internals.log.RemoteIndexCacheTest ...
BUILD SUCCESSFUL in 48m 11s

[parthikjadav]

Hi everyone! 👋

I’ve proposed a new feature that could really improve the project, and I’d love some help bringing it to life.
If anyone is interested in contributing, here’s the issue with full details:

👉 https://github.com/parthikjadav/atron-js/issues/1#event-20971767962

Your input, ideas, or PRs would be super appreciated!
Thanks in advance to anyone who wants to collaborate. 🚀

[github-actions]

A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the triage label
should be removed to prevent this automation from happening again.

[UladzislauBlok]

@chia7712 @mimaison Hello. This is fix for flaky test testConcurrentRemoveReadForCache1. Could you please take a look?

[mimaison]

Thanks for the PR