Add Seccomp profile to deployment

[WesselAtWork]

Description of changes:

I have recently tried to leveraging k8s built in Enforce Pod Security Standards with Namespace Labels feature.

When I tried to install one of the controllers I noticed warnings on the restricted profile.
This I found strange because I checked beforehand and I saw you were already dropping all the capabilities:

code-generator/templates/helm/templates/deployment.yaml

Lines 112 to 118 in 811e30b

	securityContext:
	allowPrivilegeEscalation: false
	privileged: false
	runAsNonRoot: true
	capabilities:
	drop:
	- ALL

And hard setting the host env:

code-generator/templates/helm/templates/deployment.yaml

Lines 130 to 132 in 811e30b

	hostIPC: false
	hostNetwork: false
	hostPID: false

It looks like it's just missing the scomp profile!

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[ack-prow]

Hi @WesselAtWork. Thanks for your PR.

I'm waiting for a aws-controllers-k8s member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[WesselAtWork]

I added it to the deployment template for Helm and the Config Folder.
Let me know if I missed anywhere else

[jaypipes]

Great stuff, thank you @WesselAtWork! :)

[jaypipes]

/lgtm

[ack-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jaypipes, WesselAtWork

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jaypipes]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jaypipes]

/retest