KSV030 - Doesn't trigger when no seccomp policy is specified

[raesene]

Kubernetes current default is to not set a seccomp profile on containers. At the moment KSV030 appears to only trigger when a seccomp policy or annotation is set which is not RuntimeDefault and does not trigger if there is no mention of seccomp in the manifest.