Alarm sensitivity is not handled correctly

Currently cs-web-lib uses the property `border_alarm_sensitive` to decide whether to show a widget in the alarm state. This is inconsistent with the CSS implementation where the widget always acknowledges the alarm state and the user can optionally decide to also show this as a border.

**CSS** implementation for `border_alarm_sensitive`. Note that if false it still displays the value as red indicating it is in alarm state.

**WebUI** implementation. Note that when `border_alarm_sensitive=false` we get no alarm information

Compare the WebUI handling of `border_alarm_sensitive` with the CSS behavior described in the issue, starting from the widget alarm-state logic. Done means the widget still shows its alarm state when the property is false, while the property only controls whether the alarm is also shown as a border; verify the behavior against the supplied examples.

Written by the indexing model from the issue text.