Improve UX of IO Channel-Single-Threshold Controller UI Dialog

### Component UI ### Description IMHO the dialog depicted below could benefit from some improvements. <img width="609" height="612" alt="Image" src="https://github.com/user-attachments/assets/11dc94c5-c625-4237-a140-909e9e0318c1" /> Aspects I noticed: - *state* is displayed rather subtle. It could probably be improved by an icon (as used in the widget), maybe even using additional color coding. - *mode* looks like three hierarchical identical options (on / automatic / off). In my mental model, the mode has two levels of hierarchy: i. Automatic (result can either be *on* or *off*) ii. Manual - ii.1. On - ii.2. Off - also "mode" and "action" seems kind of mixed in this UI design. I could imagine two UI controls, one to switch between manual and automatic, and a second to turn it on or off (if first element is set to manual; otherwise disable second UI control) - *threshold* has some issues with displaying the unit - the *threshold input field* seems to be too small (the current value is `300.0`, but only `3C` (3 and half a zero) is displayed) - *behavior* seems to have a hard-coded unit of `W`. - the dialog is a little too small for the contents, one row is below the fold - The *order of value and unit* is not consistent: - switched load up-down-input: unit, value - current value: value, unit (after/below -- not enough width for element?) - threshold up-down-input: unit, value - minimum switching time up-down-input: value, unit