write a page about operator packaging

[clux]

as a peripheral part of the controller guide #5 under docs/controller/packaging.md

• how to package a controller (what yaml is needed)
• helm / kubectl

helm of course has it's flaws but is ubiquitous and not too bad to generate. maybe boostraping schemas if possible.

this guide should probably be distinct from a development workflow, which is likely to use other tools like tilt/skaffold directly.

[clux]

had a quick look at this, and am increasingly getting the feeling that operatorhub is mostly for show/introductions and not practical for real world usage. I basically see a bunch of untemplateable yaml in the repo, shell installs, stuff that's wildly out of date (prom operator latest is 1y old).

Reducing the scope of this to mere packaging with helm so that we can get the basics done in a pragmatic way.

(if any openshift people want to write something on OLM (use case, benefits, what's needed, lifecycle manager) and interaction with operatorhub to prove me wrong later that's probably fine - i didn't really give it a fair chance)