[Field Definitions] Review mode for the editor: read-only settings, tree item decorator, form item annotations

[markus-moser]

Changes in this pull request

The field-definitions editor gains a review mode and two seams a consumer needs to render a proposed class definition next to its current one — without copying the editor:

• readOnly on the editor settings: the tree navigates but never rearranges (no drag & drop, no add / copy / paste / delete actions), the layout and general-settings forms render disabled, and Save, import/export and custom layouts stay out of the toolbar. useDetailUpdateMutation becomes optional.
• decorateTreeItem on the editor settings: the last word on every layout-tree item before it renders — add a status class, wrap the title.
• FormAnnotationsProvider (@pimcore/studio-ui-bundle/components): every Form.Item below it whose name is in the map renders with a status tint (added | changed | removed | moved) and an optional hint under the control. The form needs no change; the HOC sits innermost in Form.Item's chain, so the key is the resolved name path.
• The editor's inner components (EditorView, ItemsSidebar, ItemsTabs, ItemDetail, DetailSidebar, DetailContent, LayoutForm, GeneralSettingsForm) are exported from @pimcore/studio-ui-bundle/modules/field-definitions, so a consumer can compose its own view.

Tests: form-annotations.test.tsx (HOC + key), sidebar.test.tsx (edit vs review vs decorator). Storybook: Components / Data Entry / Form / Annotations.

Additional info

Gates: check-types clean, eslint clean, jest 616/616, build-sdk ok.

🤖 Generated with Claude Code

[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