Matter Switch: Add greater Energy profiling logic for Switches

[hcarter-775]

Description of Change

Update the Matter Switch driver to support the Power Topology cluster. Specifically, include support for the Node and Set features of the cluster. Update unit tests to handle this update.

Further, update powerConsumptionReport handling to only send reports to one single capability, even when there are multiple child devices getting energy reports.

Last, update energy and power handlers from emit_event_for_endpoint() calls to emit_component_event() calls to simplify handling by avoiding the weaknesses in our current endpoint_to_component() functionality.

Summary of Completed Tests

Tests updated and continue to pass.
Tested on multi-plug energy device.
Tested on single plug energy device.

[github-actions]

Duplicate profile check: Passed - no duplicate profiles detected.

[github-actions]

Invitation URL:
https://bestow-regional.api.smartthings.com/invite/WY2W4egVaylr

[github-actions]

Test Results

   67 files    442 suites   0s ⏱️
2 264 tests 2 264 ✅ 0 💤 0 ❌
3 862 runs  3 862 ✅ 0 💤 0 ❌

Results for commit f2e532c.

♻️ This comment has been updated with latest results.

[github-actions]

File	Coverage
All files	92%	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-switch/src/embedded-cluster-utils.lua	38%	❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-switch/src/aqara-cube/init.lua	96%	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-switch/src/init.lua	93%	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-switch/src/third-reality-mk1/init.lua	95%	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-switch/src/eve-energy/init.lua	92%	✅

Minimum allowed coverage is 90%

Generated by 🐒 cobertura-action against f2e532c

[nickolas-deboom]

These changes look great! I think it might be a good idea to test on some additional device types since some of the init code is being changed.

[nickolas-deboom]

I'm trying to remember but can't quite recall, I think you mentioned that these changes would result in re-profiling for certain devices that would currently not be re-profiled and just rely on fingerprints, is that the case?

[hcarter-775]

I'm trying to remember but can't quite recall, I think you mentioned that these changes would result in re-profiling for certain devices that would currently not be re-profiled and just rely on fingerprints, is that the case?

@nickolas-deboom yes, that's true. See the assign_switch_profile call at the bottom of match_profile, that will be called for all switch devices that didn't get an early return due to previous specific handling.