[Feature request]: Expose effect_colors for Aqara lumi.light.agl005, aka T2 GU10 RGB, CCT

Is your feature request related to a problem? Please describe

Description

For Aqara T2 bulbs (for example lumi.light.agl005 / T2_GU10), Zigbee2MQTT exposes dynamic effect controls:

• effect
• effect_speed
• effect_colors

The first two properties are available through the Home Assistant light entity, but effect_colors is only available through the MQTT interface.

Is this intentional, or could effect_colors be exposed to Home Assistant as an additional entity?

Current behavior

Using the Home Assistant light entity:

action: light.turn_on
target:
  entity_id: light.auffahrt_tor
data:
  brightness_pct: 100
  effect: breathing
  rgb_color:
    - 255
    - 0
    - 0

The effect starts, but the Aqara bulb does not use the requested color. It falls back to an internal/default effect color sequence.

The same effect works correctly when sending effect_colors via MQTT:

{
  "state": "ON",
  "brightness": 254,
  "effect": "breathing",
  "effect_speed": 100,
  "effect_colors": [
    {
      "r": 255,
      "g": 0,
      "b": 0
    }
  ]
}

The property is already present in the Zigbee2MQTT state:

"effect_colors": [
  {
    "r": 255,
    "g": 0,
    "b": 0
  }
]

The functionality itself appears to work correctly; the missing part seems to be exposing/configuring it from Home Assistant.

Describe the solution you'd like

It would be great if effect_colors could be made available in Home Assistant, for example as:

• a text entity containing the JSON value,
• another suitable entity type,
• or another approach that fits the Zigbee2MQTT/Home Assistant integration model.

This would allow users to configure Aqara dynamic effects without manually publishing MQTT messages.

Device information

• Manufacturer: Aqara
• Model: lumi.light.agl005
• Zigbee2MQTT definition: T2_GU10
• Firmware: 30
• Zigbee2MQTT version: 2.12.1

Great solution would sure be to just be able to use the light entity from Home Assistant in an automation but from my opinion this is to special for Aqara so would be drawn back as a feature request.

Describe alternatives you've considered

Using direct mqtt set command which works but is not the best solution as it bypasses the light entity from Home Assistant.

Additional context

none

No files or tests are named. Start by tracing how Home Assistant exposes the existing effect and effect_speed controls, then compare that path with the MQTT effect_colors state and command handling for T2_GU10. Done means an appropriate Home Assistant control can configure effect_colors for lumi.light.agl005 without manual MQTT messages.