feat: disable cache feature
What does this MR do?
Creates a boolean flag DisableCache under the CacheConfig key that if true bypasses the cache search mechanism.
Why was this MR needed?
At the moment you can't have a working runner without cache. It's weird that this is a mandatory setup.
What's the best way to test this MR?
Spin up a runner with the Kubernetes executor including the following config:
[runners.cache]
DisableCache = true
What are the relevant issue numbers?
Edited by willian.eth