HW Agent - Provide Dynamic Configuration Types for Frontend

Implement an API endpoint to obtain configuration types dynamically.

### Context

There is an attribute in the config.yaml file named: ‘orchestrator_type’. It can be used for the drop-down list.

### Previous Analysis
- The Plugin Manager reloads all configuration files for all plugins at the startup.
- The attribute ‘orchestrator_type’ is an open text (see plugin_definition_schema.json)
- The name of the plugin directory must be unique and could perhaps be the key.

### Considerations about using the subfolder name instead of orchestrator type

**Unique Plugin Identity**
Using the subfolder name or a dedicated plugin ID guarantees that every plugin is uniquely identifiable. This is essential for the Plugin Manager to load and manage plugins without collisions.

**Future Extensibility**:
This design is more scalable. If you later decide that certain orchestrator types have preferred or default implementations, you can add an extra field (e.g., “default: true”) without affecting the core uniqueness of the Plugin.

cc @soniasantiago, @tranchis