Device Type Requirements from One Endpoint Affecting Another Unrelated Endpoint

[ethanzhouyc]

Steps to reproduce:

1. run ZAP in Matter mode
2. create Endpoint 1 with device type Extended Color Light
3. create Endpoint 2 with any device type (e.g. Door Lock) with Color Control cluster disabled by default
4. Enable Color Control cluster in Endpoint 2
5. Device type compliance warnings appeared in the notification pane as below

Issue:
It seems that the requirements associated with the Extended Color Light device type, Color Control cluster in Endpoint 1 are incorrectly influencing Endpoint 2. As a result, attributes and commands not enabled by default in Endpoint 2 trigger incorrect device type compliance warnings.

Assumptions:
The related triggers could have been written when only Zigbee was our priority or just tested on Zigbee. In Zigbee the cluster configurations are shared across clusters. So enabling color control in Endpoint 2 would have made it the same as the one on Endpoint 1