Rethink action enabled state and its presentation
Currently every action can be enabled/disabled in the KCM. Disabling the action causes the plugin to not be loaded.
For some actions it makes sense to "disable" them. For example for the brightness action you want to be able to say "leave the current brightness untouched when changing profile". Or you want to completely disable automatic suspension.
For other actions it makes less sense since there is an inherent null/no-op configuration. For example setting button handling to "do nothing" is functionally the same as disabling the button handling altogether. Power profiles also has a "Leave unchanged" option that works as if the action was disabled.
Currently every action gets a checkbox in the KCM. For those with an inherent no-op config this is redundant and confusing.
On a visual level we should improve the presentation of such actions.
On an implementation level, instead of having the enabledness of actions baked into the core infrastructure we might want to instead always load all actions (if supported by the hardware) and manage enabledness internally for those where it makes sense