feat: configuration templates

[robertsLando]

Discussed in #4515

Actually we already identify existing devices types in our zwave client by using _getDeviceID function and storing them into devices prop.

This feature requires to define custom devices templates based on this prop plus also a minimum firmware version (it should be easy to update template to newer version of firmware)

Template Creation

• A template can be created from an already-configured device. There should be a dedicated button like "Create template" in node advanced dialog
• The template contains configuration parameters (CC 112)
• templates should be stored on store directory under configurationTemplates.json
• templates should be included in backup/restore files
• It should be possible to import/export this JSON. The import/export can be placed on general advanced actions

Applying Templates

Once created it should be possible to apply template to all existing identical devices
per device, per setting local override

When a new matching device is included:

• zwave-js-ui detects the match
• prompts to apply the template (or auto-applies if enabled in settings)

When a device is replaced:

• the same template is reapplied automatically

[robertsLando]

cc @AlCalzone

[AlCalzone]

It sounds like this would pair really well with this feature idea, which would allow setting the parameters during the initial interview:
zwave-js/zwave-js#6781

[robertsLando]

@AlCalzone Are you ok with all the things I wrote above or would you suggest to change/add something? Otherwise I will let copilot draft it