Consider moving to ComponentConfig instead of CLI flags

[font]

kuberbuilder v3, what operator-sdk v1.3.2 is based on, defines the ability to use ComponentConfig to pass additional configurations into the operator instead of relying on cli flags parsed by main.go. Since the Kubernetes community has been migrating the core components away from this and toward using versioned config files, referred to as "component configs", we should consider doing the same.

The move to operator-sdk v1.3.2 already provides the bootstrapping capabilities to generate the ConfigMap using the ControllerManagerConfig manifest, along with the kustomization rule to patch the manager deployment using manager_config_patch.yaml. What's remaining is the need to add a flag to the operator to identify the name of the ConfigMap so that the operator controller can read it in to parse the options. See https://master.book.kubebuilder.io/component-config-tutorial/tutorial.html for more details.