Unit testing support for Dependent Resources

[csviri]

Support for unit testing (mocking) should be improved for dependent resources. Currently for example for CRUDKubernetesDependentResource is calling eventsource().getSecondaryResource to load the actual state from cache. Eventually this as described on other issues:

#1175
#1240

might be better to call context.getSecondaryResource().

With this we could actually make it easy to support cache state for unit tests.

But we should also create examples, and support for client mocking.

Acceptance Criteria:

• Can developers easily mock context.getSecondaryResource (assumption is used in dependent resources - but useful in general)
• Can developers easily mock Kubernetes Client for other operations.
• Is there a example showcasing unit testing

[csviri]

The problem here is that now dependent resources use also event source under the hood, (not to read the resource but to make sure some of the updates end up in the caches and similar tricks). It is quite hard to mock that all. But also conceptually, the framework tests dependent resources, so its kinda made sure those are tested. All the addition user does can be (desired state, matchers) tested separatettly by an unit test, what is trivial.