kube: use native seccompProfile fields

[jiwahn]

Fixes: #27501

Checklist

Ensure you have completed the following checklist for your pull request to be reviewed:

• Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
  commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
  the sign-off email address. See CONTRIBUTING.md
  for more information.
• Referenced issues using Fixes: #00000 in commit message (if applicable)
• Tests have been added/updated (or no tests are needed)
• Documentation has been updated (or no documentation changes are needed)
• All commits pass make validatepr (format/lint checks)
• Release note entered in the section below (or None if no user-facing changes)

Does this PR introduce a user-facing change?

Podman kube play now uses Kubernetes securityContext.seccompProfile fields for seccomp configuration instead of the deprecated Kubernetes seccomp annotations.

Description

Instead of using the deprecated seccomp annotations for seccomp configuration, this now uses the native securityContext.seccompProfile field. Removed seccomp.go because annotations no longer need to be parsed before generating the spec. Unit tests have also been added.

[TomSweeneyRedHat]

@lsm5 PTAL

[TomSweeneyRedHat]

The changes look good to me in general