feat (rgbcw_lightbulb): add Cree CMA21-100W-AL-9ACK

[ide]

Why

The Cree Connected Max A21 100W smart bulb (https://www.lowes.com/pd/5001171499) uses Tuya and matches the rgbcw_lightbulb config but has no product ID entry, so it falls back to DPS-based matching and incorrectly matches calex_s45cleare27_light at 88%.

How

The product ID e8dhekwuvrdogter was obtained from the Tuya IoT Platform cloud API (/v2.0/cloud/thing/batch) and confirmed with tinytuya scan, which reported the device as v3.3 at the same address and device ID.

The device reports DPs 20, 21, 22, 23, 24, 25, 26, and 41, which match the rgbcw_lightbulb config (DPs 20–28, 30–32, 34). The instruction set from the Tuya IoT Platform confirms the standard RGBCW schema: switch_led, work_mode (white/colour/scene/music), bright_value_v2 (10–1000), temp_value_v2 (0–1000), colour_data_v2 (HSV), scene_data_v2, countdown_1, music_data, control_data, rhythm_mode, sleep_mode, and wakeup_mode.

Test Plan

Configured the device in tuya-local with protocol version 3.3 and type rgbcw_lightbulb. The device connects and I can control the bulb.

[make-all]

Sorry, it sounds from the description like it DOESN'T match the rgbcw_lightbulb, instead the closest match is an 88% match for calex_s45cleare27_light. So adding the product id to rgbcw_lightbulb may not be the correct action.
I need to see the full dps matching log message and preferably the Query Things Data Model result for the device, to confirm any dps that are supported but not being sent at the time of matching.

[ide]

Sorry, to clarify: this bulb should be identified as rgbcw_lightbulb but Tuya Local isn't making that association.

The Cree Connected Max A21 bulb has RGB + white color temperatures. It does not look like a Calex S45 bulb, which doesn't have RGB from the photos I see online.

I'll debug some more. It could also be that the calex_s45cleare27_light entry has the name "Cree" in it and that's influencing the matching heuristic.