feat(25881): Add Device Tag management to the workspace

[vanch3d]

See https://hivemq.kanbanize.com/ctrl_board/57/cards/25881/details/

This PR is part of the bi-directional epic and introduces basic management for the Device Tags in the workspace

Device Tags are the first level of abstraction of the device-to-MQTT mapping flow, in which users create a unique name (the "tag") for a specific address of a data point on the device.

Design

• The tag management has been moved to the devices on the workspace It is available by clicking on the device node or on the CTA, opening the configuration side panel
• The side panel is intended to provide all information pertinent to its contextualization, including the tags
• The tag name is expected to be unique across the Edge instance and to follow the segment pattern used for topics
• The tag address will differ from device to device but will be a list of attribute values that uniquely define a data point on this device
  • { node: 'ns=3;i=1008' } for opc-ua
  • { startIdx: 0, index: 1 } for modbus
• The management of tags is split into two distinct operations:
  • visualisation of the existing tags in a list
  • management of the tags (creation, modification, deletion) in a separate, JSONSchema-based form

Out-of-scope

• The schema of the tag address is extracted through "magic" fromthe JSON-Schema of the adapter config. This is neither safe nor sustainable and it should be provided by a refactored payload, see https://hivemq.kanbanize.com/ctrl_board/57/cards/26668/details/.
• The devices don't exist as an Edge entity and therefore don't provide any pertinent information to display (the few information points are inferred from their adapter). The panel contains a "metadata" viewer that is a non-interactive placeholder. It will be refactored in further tickets (and initiatives)

Before

After