feat: support Sunricher SR-ZG9030A-MW

[niracler]

Notably

While developing support for Sunricher devices, I discovered a ModelId conflict between two devices in their product line. To resolve this, I implemented an expose that allows users to switch the ModelId. This implementation required skipping the set/get access check in the test cases.

I'm not entirely confident if bypassing the test case through this approach is the best solution. I would appreciate your feedback and suggestions for potential improvements.

Reference code showing the ModelId conflict handling:

const sunricherTz = {
    setModel: {
        key: ['model'],
        convertSet: async (entity, key, value, meta) => {
            await entity.write('genBasic', {modelId: value});
            return {state: {model: value}};
        },
    } satisfies Tz.Converter,
};

And the test case bypass:

if (device.toZigbee.includes(sunricher.tz.setModel)) return;

[Koenkk]

Where is this used for? (what does changing the modelId do)

[niracler]

Some ZG9030A-MW devices were mistakenly set with the modelId HK-DIM during manufacturing. Therefore, we need to provide a method that allows users to update the modelId of these HK-DIM devices to ZG9030A-MW.

[Koenkk]

Thanks!