Setup security context of controller deployment, enforce restricted PodSecurity in namespace

[SaschaSchwarze0]

Changes

This pull request configures the security of the controller deployment to fulfill the restricted PodSecurity profile. The namespace is configured to enforce this. The KinD configuration is updated to enable PodSecurity admission. I also update the KinD version to be current. I had to change the e2e that we run here in GitHub to use its own namespace because build strategies like Kaniko require elevated permissions beyond privileged. And in general, we should have never used this namespace imo. I also updated the documentation in that regard.

Fixes #1331

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Set a kind label on this PR
• Release notes block has been filled in, or marked NONE

Release Notes

The shipwright-build namespace is now configured to enforce restricted PodSecurity. The shipwright-build-controller deployment was updated to fulfill all requirements.

[qu1queee]

nice!

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

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 [qu1queee]

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