Reimplement webhook logic on top of kubebuilder-generated webhook

[MirahImage]

The projects-operator has a custom-built webhook that is serving CREATE project and CREATE/UPDATE projectaccess. While doing this work we created a standalone binary and manually wired it all up in our helm templating.

However it seems like kubebuilder has some pretty sweet support for webhooks, so it might be nice for us to buy into this.

Acceptance

• project-operator acceptance tests all pass
• we are using a kubebuilder webhook, not a custom manual one

[gmrodgers]

The webhook supports looks pretty awesome. It provides create,update and delete methods on the api resources that will be called when the appropriate endpoint is hit to trigger the webhook. Unfortunately the abstraction covers up Request and therefore the userInfo which we use in two of our resources so we cannot move over until we can get access to these.