On `AbstractButton::checked` property set to true, the button property AbstractButton::checkable is forced to `true` too.

This behavior was introduced to simplify buttons setup:

    Button { checked: true }

    Button { checkable: true }

(the first button is forced to be checkable)

ItemDelegate inherits this behavior but unfortunately, 'checkable' delegates are not fully compatible with models: The model API provides a means to reject the data change (QAIM::setData() can return 'false' ). In that case, a checkable delegate state will get out of sync, because the delegate changes its state on the user action.
To make the delegate correctly work with non-trivial models, the delegate should be kept uncheckable. On the Qt side, there is a code that forces the Delegate to be checkable on the (binded) model data changed to true.

The following unidirectional data flow should take its place:

1. The delegate state always represents the model data.
2. On the user action, the delegate requests the model to adjust the data.
3. The model validates and performs the request.
4. The model notifies the views about the data changes via the standard Qt API (dataChanged signal).
5. The delegate updates its state on dataChanged() signal received.

The "Setting checked to true forces checkable property to true" behavior added to save one property setup in trivial cases, results in the need to revert the forced "checkable" property changes in model-driven AbstractButton instances (such as CheckDelegate, SwitchDelegate and customized ItemDelegate).

The workaround is line `onCheckableChanged: checkable = false` added to all checkable delegates driven by models. See also example in the attachment (Qt 6).

The workaround is needed because on the model data changes the current Qt code rolls back explicitly set 'checkable' to from 'false' to 'true' (and uncheckable delegate is the only way to work with models)