Remove redfish specific config if kepler is deployed without redfish

Currently, if Kepler is deployed without redfish the config map that gets created still exposes redfish-related properties. For eg:

~ ❯ oc get kepler kepler -o jsonpath="{.spec}" | jq; oc get cm -n kepler-operator kepler -o jsonpath='{.data}' | jq
{
  "exporter": {
    "deployment": {
      "nodeSelector": {
        "kubernetes.io/os": "linux"
      },
      "port": 9103,
      "tolerations": [
        {
          "operator": "Exists"
        }
      ]
    }
  }
}
{
  "BIND_ADDRESS": "0.0.0.0:9103",
  "CGROUP_METRICS": "*",
  "CPU_ARCH_OVERRIDE": "",
  "ENABLE_EBPF_CGROUPID": "true",
  "ENABLE_GPU": "true",
  "ENABLE_PROCESS_METRICS": "false",
  "ENABLE_QAT": "false",
  "EXPOSE_CGROUP_METRICS": "true",
  "EXPOSE_HW_COUNTER_METRICS": "true",
  "EXPOSE_IRQ_COUNTER_METRICS": "true",
  "EXPOSE_KUBELET_METRICS": "true",
  "KEPLER_LOG_LEVEL": "1",
  "KEPLER_NAMESPACE": "kepler-operator",
  "METRIC_PATH": "/metrics",
  "MODEL_CONFIG": "",
  "REDFISH_PROBE_INTERVAL_IN_SECONDS": "60",
  "REDFISH_SKIP_SSL_VERIFY": "true"
}

sustainable-computing-io / kepler-operator

Remove redfish specific config if kepler is deployed without redfish #376