Lifecycle ts: fix to avoid some checks to be skipped.

[greyerof]

The WithSkipCheckFn works doing OR (default behaviour) or AND operations with all the skip functions that have been passed. It's not possible to mix them, so I had to create a helper function to check whether both the env.Deployments and env.StatefulSets slices are empty.

Examples:

check1.WithSkipCheckFn(skipFn1, skipFn2)

check1 will be skipped if any of those skip functions return true (OR op because check.SkipMode=SkipModeAny by default).

check2.WithSkipCheckFn(skipFn1, skipFn2).
       WithSkipModeAll()

check2 will be skipped if both skipFn1 and skipFn2 return true (AND op = check.SkipMode=SkipModeAll).

Also:

• Some refactor was done in the lifecycle-pod-recreation check to create deployments and statefulsets compliant/nonCompliant objects lists.
• Added skip functions for the lifecycle-storage-provisioner and set pod as compliant if it's not using any pvc/storageclass. This is a non-backward-compatible change as now the check will be skipped instead of passed in those cases.
• Added passing checks from lifecycle and networking test suites to the gradetool's policy json.

ToDos:

• refactor the testPodsRecreation() check function to avoid the cyclomatic complexity linting issue.
• refactor the testStorageProvisioner() check function to add some short-circuits to avoid the for-if-for-if-for-if... pattern.