Description of problem: ======================= The infraEnv controller doesn't have a way to know how many NMStateConfigs to anticipate. Since the controller watches for NMStateConfig changes and invokes image regeneration per each NMStateConfig addition/removal/update, it would help to log the amount of NMStateConfigs in each image generation.
Verified with: assisted-service: quay.io/ocpmetal/assisted-service@sha256:2706a902016fdbda8ca61a69052f22275d51f9cbbc18e877fb34d83055949d82 time="2021-06-08T06:21:56Z" level=info msg="the amount of nmStateConfigs included in the image is: 5" func="github.com/openshift/assisted-service/internal/controller/controllers.(*InfraEnvReconciler).ensureISO" file="/go/src/github.com/openshift/origin/internal/controller/controllers/infraenv_controller.go:286" go-id=648 infra_env=multinode-infraenv infra_env_namespace=assisted-installer request_id=02d9fc73-b994-4d0f-8cad-f3717f46ff65