Create OCP project template and add organization label to projects

[simu]

This PR configures a custom OCP project template which only creates a Project resource and no rolebindings.

The PR also adds a mutate policy which adds the requesting user's default organization to the project based on the value of annotation
openshift.io/requester on the Project resource created by the OCP project template.

Additionally, we refactor the code a bit since this new mutate policy is mostly identical to the one which handles setting a default organization when users create projects with kubectl create ns.

Checklist

• Keep pull requests small so they can be easily reviewed.
• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog

[ccremer]

Do these policies also work when using a Project spec from YAML (e.g. oc create -f project.yaml) ?
I ask because I'm not sure if a YAML spec is the same as oc create project because the oc binary might do more magic in the background (e.g. creating a ProjectRequest instead).

I really have no idea if there's a difference between the two, just asking here.

[simu]

Do these policies also work when using a Project spec from YAML (e.g. oc create -f project.yaml) ?

They don't have to, because regular users cannot oc create -f project.yaml anyway.

[ccremer]

They don't have to, because regular users cannot oc create -f project.yaml anyway.

How so? I could imagine some Kustomize or CI/CD use cases for this?

[simu]

They don't have to, because regular users cannot oc create -f project.yaml anyway.

How so? I could imagine some Kustomize or CI/CD use cases for this?

In CI/CD, users can use the Namespace resource which they do have permissions to create. Out of the box, regular users don't have permissions to directly create Project resources on OpenShift.