Profile load/unload events only make sense in the context ofswitching between power state profiles, which can't happen unlessbattery profiles are supported on the given system.
For a system with only "AC Power", let's not show the correspondingprofile load/unload custom script fields in the KCM. This only leavesthe idle timeout custom script, which in this case we may as wellshow unconditionally and take out the "Choose run conditions" button.
In the C++ backend, the code for querying Solid for batteries getsmoved to the KCM constructor so that kcm.supportsBatteryProfilesis correct at QML component construction time already.