Handle situations when we cannot collect or list particular resource(s)

[im-konge]

Description

This PR adds additional method that handles execution of the collect/list/describe methods and their error handling. In situations when LogCollector lists the resources for particular type and gets the full list of names, it then tries to collect YAMLs for each of the resource in that list. However, in case that the resource was deleted in the meantime, it fails with the exception that particular resource with name in Namespace doesn't exist, failing the whole LogCollector and the collection of the data.

This execution method takes lambda with the method that should be executed and, in case that there is some exception, it just logs that it couldn't collect the stuff, because of the issue, but stays up and tries to collect other resources.

Fixes #98

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit/integration tests pass locally with my changes