feat: add new container security rules for NoNewPrivileges and SeccompProfile

[juev]

• Introduced NoNewPrivilegesRule to ensure containers do not allow privilege escalation.
• Added SeccompProfileRule to validate seccomp profiles for containers, ensuring proper security configurations.
• Updated linters settings to include new exclusion rules for NoNewPrivileges and SeccompProfile.

Example:

🐒 [no-new-privileges (#container)]
     Message:      Container's SecurityContext is missing - cannot verify allowPrivilegeEscalation setting
     Module:       kube-dns
     Object:       kind = Deployment ; name = d8-kube-dns-sts-pods-hosts-appender-webhook ; namespace = kube-system ; container = webhook
     FilePath:     templates/sts-pods-hosts-appender-webhook/deployment.yaml

🐒 [seccomp-profile (#container)]
     Message:      No seccomp profile specified - consider explicitly setting seccompProfile.type to 'RuntimeDefault'
                   for better security posture
     Module:       kube-dns
     Object:       kind = Deployment ; name = d8-kube-dns-sts-pods-hosts-appender-webhook ; namespace = kube-system ; container = webhook
     FilePath:     templates/sts-pods-hosts-appender-webhook/deployment.yaml