We are currently moving away from using our components inside each other and instead provide slots for such cases (see #188 and #222).
This way we don't have to mirror the API of the component used in it and make it more flexible for the consumer as they have full access to the API of the slotted component.

This also applies to the ino-control-item where we are using the ino-list-item.

There are two possible solutions to this:

1. Provide Slots inside the ino-list-item where the consumer can provide a checkbox or a radio button and move the logic from the ino-control-item to the ino-list-item. This would make the ino-control-item obsolete.

See also #522