Need a way to disable experimental feature profileCustomizations.devLowNodeUtilizationThresholds at the begining of KubeDescheduler CR configuration. 

Kube Descheduler Operator 4.12.0-202309181625 provided by Red Hat, Inc.

Always

1. Install de-scheduler operator inside namespace 'openshift-kube-descheduler-operator' namespace
2.  Kube Descheduler tab and click Create KubeDescheduler
3. Select form method:
 -  change the Mode field to Automatic
 -  Add the required profiles
 -  Expand the Profile Customizations section to set optional configurations for the descheduler.
 - Here we want to add 'podLifetime' value for 'LifecycleAndUtilization' only and we do not need experimental feature 'devLowNodeUtilizationThresholds'. But still 'devLowNodeUtilizationThresholds' value is getting added even if we remove the default value 'Medium' and set as 'Null'.
 
4. Verify 'profileCustomizations' section:
---------------
  operatorLogLevel: Normal
  profileCustomizations:
    devLowNodeUtilizationThresholds: Medium        <----
    namespaces: {}
    podLifetime: 4368h0m0s
  profiles:
  - AffinityAndTaints
  unsupportedConfigOverrides: null
  --------------- 

1. Experimental feature profileCustomizations.devLowNodeUtilizationThresholds  is getting configured inside KubeDescheduler CR
2. We need to edit KubeDescheduler CR again to remove profileCustomizations.devLowNodeUtilizationThresholds field and save the CR

Experimental feature profileCustomizations.devLowNodeUtilizationThresholds should not get added automatically when we try to add other fields from profileCustomizations section.