Support to manually trigger CacheStore._cleanupCache()

## 🚀 Feature Requests

Support to manually trigger CacheStore._cleanupCache()

### Describe the feature
In current CacheStore implementation _cleanupCache() function is triggered 10 seconds later after every call to CacheStore.retrieveCacheData function. That means; if we don't request a new -not yet cached uri-, retrieveCacheData function will not be triggered, so there is no way that _cleanupCache logic have a chance to run again.

As I understand correctly; in current implementation there is no way to get a new version of an already cached url resource till we request a new uri resource to trigger cleanup logic.

### Platforms affected (mark all that apply)
- [x] :iphone: iOS
- [x] :robot: Android

首先跟踪 CacheStore.retrieveCacheData 和延迟的 _cleanupCache() 调用，以了解当前何时运行清理。定义手动触发器对已缓存 URL 的预期行为，然后验证无需请求新的 URI 即可调用清理，并通过相关的 cache-store 测试覆盖此行为。

由索引模型根据 Issue 内容生成。