Migrate to an operator pattern instead of helm-based values

[maxhoesel]

Right now, this utility is pretty simplistic and limited in what it can do:

• A single deployment can only manage a single pool
• The pool has to already exist
• Modifying the pool without owning it breaks the typical k8s control cycle and makes using IaC tools such as Terraform problematic

For a future revision of this tool, i'd like to rewrite it as a k8s operator that operated on a Custom Resource: Dyn6AddressPool. This CRD would serve as a template for a real address pool resource managed by the operator, in the same way that Bitnamis SealedSecrets or the standard Deployment -> Pods work. Since this is a rather substantial effort, it probably wont happen anytime soon however