Automation switch targets and the Settings bind row are Zigbee-specific; generalise to lane-tagged devices

The rule action zigbee_switch keys on a zigbee2mqtt friendly_name, the actuatable list at /settings/zigbee/actuatable was Zigbee-only, and the binding validators plus ZigbeeBindRow were embedded in the Zigbee module. PARTLY DONE 2026-09-07 (Tuya T1): shared brain/dsc_brain/device_bindings.py (VALID_ZONES, CLASS_ROLE_KINDS, normalize_binding, cross-lane role_conflicts) used by both lanes; lane-tagged GET /settings/devices/actuatable ({lane, id, friendly_name, alias, role, device_id|ieee}) with the Zigbee route kept; rule editor lists Zigbee switch and Tuya plug as separate actions fed from the one lane-tagged list. REMAINING: ZigbeeBindRow is reused by the Tuya card as-is (device id passed through the ieee prop) — rename to DeviceBindRow with a lane prop when the S5 Devices restructure touches it; a single ‘Switch a plug’ picker that writes whichever action type the lane needs is still two options today.