Fix link field subtype/class restriction config UI and editor enforcement

[Copilot]

The three new MultiSelect widgets for asset/document/object subtypes in the Link class definition UI were missing name, value, and fieldLabel — so restrictions were never persisted or displayed. Additionally, the link editor panel (helpers.js) had no logic to enforce subtype or class filters during drag-and-drop or item selector search.

Changes

object/classes/data/link.js

• Added fieldLabel, name, id, and value: this.datax.* to the three subtype MultiSelects so values are persisted and pre-populated
• Map all plain string array stores (including existing allowedTypes, allowedTargets, disabledFields) to {text} objects so displayField/valueField: "text" resolve correctly

object/tags/link.js

• Initialize config as {} instead of []
• Build and forward allowedSubtypes (keyed by element type) and allowedClasses into the editor config

helpers.js — openLinkEditPanel

• Add SUBTYPES constant (asset/document/object search types, folders excluded)
• Derive allowedSubtypes and allowedClasses from config
• Introduce dndAllowed(data) to gate drag-and-drop on type + subtype + class
• Pass subtype and specific.classes to the item selector search

translations/admin_ext.en.yaml

• Add allowed_asset_subtypes, allowed_document_subtypes, allowed_object_subtypes keys (previously referenced but missing)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud