Enforce: allowEditInvariantFromNonDefault configuration in the Backoffice UI

[madsrasmussen]

This PR fixes the implementation of the allowEditInvariantFromNonDefault config.

This now means that when allowEditInvariantFromNonDefault is false, it won't be possible to edit invariant culture fields from other cultures than the default.

Fixes: #19241

[Copilot]

Pull Request Overview

This PR aims to enforce the new behavior for the allowEditInvariantFromNonDefault configuration by preventing the editing of invariant culture fields outside the default language.

• Removed configuration-based editing logic from the document workspace context.
• Introduced invariant editing prevention logic into the document property dataset context.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/Umbraco.Web.UI.Client/src/packages/documents/documents/workspace/document-workspace.context.ts	Removed obsolete configuration consumption and prevention logic.
src/Umbraco.Web.UI.Client/src/packages/documents/documents/property-dataset-context/document-property-dataset.context.ts	Added enforcement for invariant editing prevention using variant options and property rules.

Comments suppressed due to low confidence (1)

src/Umbraco.Web.UI.Client/src/packages/documents/documents/property-dataset-context/document-property-dataset.context.ts:47

• The rule unique identifier naming here is different from the earlier approach in the workspace context. Consider consolidating the naming conventions (e.g., using consistent casing and format) across modules to improve clarity.

const unique = 'UMB_PREVENT_EDIT_INVARIANT_FROM_NON_DEFAULT_' + property.unique;

[nielslyngsoe]

beautiful