[WIP - testing] Add resource version parameter for kubernates strategy

[Argonus]

Summary of changes

Why

In enviroment with multiple different application, using same kubernates cluster, many apps may trigger thousends of requests to cluster API to get requested resources. In our case, we talk about 500000 requests per hour. In such a case, direct requests to etcd may impact cluster resources. Solution for such a case may be

• using cached version of resource (implemented in PR)
• using watch to subscribe to changes (investigating possible solutions)

In this PR, as cache should be eventually consistent, I've implemented simples solution for such a issue, aka using cached version of resource instead of direct API call. According do AWS, which is our cluster provider, cache inconsistency should be few tens of milliseconds

What

• Add kubernetes_resource_version parameter to Kubernates strategy, that allows to select given resource version, in our case, select 0 as a cache.
• Added test cases for extended api call.

Checklist

• New functions have typespecs, changed functions were updated
• Same for documentation, including moduledocs
• Tests were added or updated to cover changes
• Commits were squashed into a single coherent commit
• Notes added to CHANGELOG file which describe changes at a high-level