Feature: add callback data to the bridge device type callback (CON-989)

[Ravenen]

What

I have added callback data to the bridge device type callback (esp_matter_bridge::set_device_type). Correspondingly, callback data has been integrated into the esp_matter_bridge::create_device and esp_matter_bridge::resume_device functions.

Why

This enhancement allows for the efficient transmission of type-specific configuration data to the device during its creation. This is particularly beneficial in scenarios where passing such information to the priv_data parameter might not be ideal. The priv_data parameter, typically passed to endpoint metadata and other callbacks like attribute_callback, can now be kept separate from configuration details.

Use-case

In my specific use-case, I have implemented an abstraction layer above esp-matter. When a device is created, I aim to transmit both application user context (device object with application meta-data) and Matter-specific configuration (e.g., features for a generic switch). By utilizing the callback data, I can achieve a clean separation between priv_data and configurations within the abstraction layer. This proves to be advantageous as the abstraction layer does not need to be aware of the context structure in priv_data, resulting in a more organized and maintainable codebase.

I believe that this enhancement aligns with common use-cases where developers desire to keep priv_data and configurations distinctly separated.

[CLAassistant]

All committers have signed the CLA.