feat: add scene handling (move from ZHC)

[Nerivec]

Move scene handling to ZH (spec).
Main goal is to better sync state/scenes so we don't get as many mismatches in e.g. frontend.

• Adds missing barrierControl & hvacThermostat clusters with respective scene-capable attributes (per R8 spec)
• Use more advanced sync mechanisms (depending on request)
  • scene from Zigbee
  • scene from state (clusters cache)
  • state (clusters cache) from scene
• Sync all clusters/attributes (ZHC did only a subset)
• Unicast sync done using view command to save "as it is on device" [subject to change, may not be necessary, needs actual tests]
• Groupcast sync done locally on "best-effort" (no feedback on request, many view requests required otherwise)
• Remove scenes on group(s) removal according to spec
• Add migration from .meta.scenes to .scenes for database
• Fix a somewhat dangerous shallow endpoint.clusters clone in Device (no cloning needed at all).

TODO:

• Z2M API endpoints and converter bypass for old scene stuff
• ZHC cleanup (remove all converters, remove auto-added converters on devices)
• State publishing on recall (what old recall converter did)
  • Investigate possible friction with devices using recall off-spec
• Handle state (sync/publish) when transition time is involved (either via recall override or in underlying state)

CC: @MfCrizz

[Nerivec]

@Koenkk any initial thoughts on this?
For the Z2M part, could add a dedicated extension or just do pass-through in bridge.

[Koenkk]

@Nerivec similar to groups, I agree this also deserves to be in zigbee-herdman indeed, code looks good to me!

[Nerivec]

@Koenkk can you take a look at the code before I start working on missing coverage? Cleaned up quite a bit, improved typing. I think it's about right?

For the Z2M/ZHC update, we're going to need new MQTT API endpoints (bridge/request/scene/*).
We also add tempory bypasses (deprecated for 3.0) in Z2M to call ZH API directly instead of going to converter when the old API is used (e.g. old frontend). This would allow proper ZHC cleanup (remove per-device converters for scene stuff).

[Koenkk]

LGTM!

Only question; how are we going to publish an updated state? Basically what is now done through the recalledState here.

[Nerivec]

Haven't gotten that far yet. Still need to figure out the details for Z2M/ZHC... 😅

Also have to handle the transition time better I think (should not publish scene state immediately when it won't be like that for possibly several seconds). I figure some devices will already report parts of the state on their own (stuff that's configured in reporting). Have to check what they do when transition time is involved (do they publish at start or end of timer, or several times in-between). Need to de-conflict this.