[JohanBendz]

Coding batch 6: isolated standard IAS Zone motion + ZCL illuminance

Adds TWO distinct exact Homey Compose identities from independent physical Homey interviews:

• _TZE200_kb5noeto / TS0601: original interview in historical PR Add _TZE200_kb5noeto to motion_sensor_2 (PIR 24GHz radar) #1122 plus Device Request - PIR 24Ghz human presence sensor battery operated - _TZE200_kb5noeto / TS0601 #942 and Device Request - [Device name] - [Tuya] / [ZG-204ZS / ZG-204ZM] #1064, IAS zoneType motionSensor, EP1 Basic0/Identify3/Power1/Illuminance1024/IAS1280 without EF00, unlike existing frozen motion_sensor_2 runtime.
• HOBEIAN / ZG-204ZL: original full physical Device Request - Zigbee PIR Sensor with lux - HOBEIAN / ZG-204ZL #1267, same standard EP1 and actual IAS zoneType motionSensor, separate exact model and HOBEIAN pairing. Do NOT confuse with interview-less ZG-204Z without trailing L (Device Request - HOBEIAN ZG-204Z PIR motion sensor - exact Homey Zigbee identity needed #1275).

Two independent exact manufacturerName/productId driver profiles (motion_lux_kb5noeto, motion_lux_hobeian_zg204zl) with a newly isolated reusable standard-cluster runtime. Handles IAS motion set/clear with partial flags safeguarded, IAS battery flag, reactive enrollment fallback, standard Power1 batteryPercentageRemaining (0..200 / 2; reject 0xff), ZCL Illumination measuredValue with existing unchanged logarithmic helper. Optional first-initialization reporting failures for sleepy sensors are nonfatal. No EF00/vendor datapoint code, no existing/legacy light/global Zigbee driver modifications, no auto-clear timeout without observed physical evidence.

Actual battery cell type/count for BOTH unknown despite observed 3.0V, hence OTHER. Standard logarithmic lux interpretation is provisional: physical interview 33k raw / maxMeasuredValue 4000 must be calibrated against real light levels in PUBLIC 0.4 Test. Individual motion/cooldown, clear, lux, Flow, battery, wake/rejoin acceptance rows; no claim of working hardware prior to Test.

Safety exception found during triage: eWeLink/SNZB-03 source #1113 is identical public manufacturer/product for a separate water sensor #1475. This PR intentionally does NOT add an unsafe ambiguous driver for that identity or uncertain-scope iHorn #925. Existing Sonoff SNZB-04 contact code remains unchanged.

Includes mock behavior and exact matcher/negative matching tests, Homey Compose app.json, generated supported-device index, changelog and physical Test readiness. Candidate after merge: 154 total drivers, 19 isolated new 0.4 profiles, 33 exact physical identity acceptance rows. Keep #1481 OPEN for per-identity public Test; do not change frozen 0.3.1, PR #1470 or release channel. Refs #1481, #1267, #1113, #1475, #1469.