Uses an ugly hack to get the readonlyGuard to work nicely in 16.0.0

Once 16.1.0 out and this PR is in CMS - then remove this HACKY workaround
umbraco/Umbraco-CMS#19621

Still need to use readonlyGuard for the node name readonly and its not deprecated by core yet as they still use it

Author: warrenbuckley

ContentLock/Client/src/workspaceContexts/contentlock.workspace.context.ts

@@ -31,6 +31,8 @@ export class ContentLockWorkspaceContext extends UmbContextBase {
 
     #localize = new UmbLocalizationController(this);
 
+    #isSettingNameHack = false;
+
 	constructor(host: UmbControllerHost) {
 		super(host, CONTENTLOCK_WORKSPACE_CONTEXT.toString());
 
@@ -109,6 +111,14 @@ export class ContentLockWorkspaceContext extends UmbContextBase {
                     this.#docWorkspaceCtx?.readOnlyGuard.removeRules(ruleKeys);
                 }
 
+                // TODO: Remember to remove this once PR merged in
+                // https://github.com/umbraco/Umbraco-CMS/pull/19621
+                // Call the MEGA HACK workaround in a separate method
+                // ================================================================
+                this.#runSetNameHack();
+                // ================================================================
+
+
                 // If previously the page was locked by someone else, we can alert the user its now unlocked
                 if (previousState.isLocked && !previousState.isLockedBySelf && !isLocked && !isLockedBySelf) {
                     umbOpenModal(this, UMB_CONFIRM_MODAL,
@@ -162,6 +172,44 @@ export class ContentLockWorkspaceContext extends UmbContextBase {
 	public setLockedByName(lockedBy: string) {
 		this.#lockedByName.setValue(lockedBy);
 	}
+
+    // ================================================================================================
+    /**
+     * TODO: REMEMBER TO REMOVE THIS
+     * Temporary workaround for Umbraco bug see https://github.com/umbraco/Umbraco-CMS/pull/19621
+     * Forces the workspace name to update to avoid UI issues when unlocking.
+     * Thanks to Mads for the idea/hack for now
+     */
+    #runSetNameHack() {
+        if (this.#isSettingNameHack){
+            return;
+        }
+
+        this.#isSettingNameHack = true;
+        
+        try {
+            const currentName = this.#docWorkspaceCtx?.getName();
+            if (!currentName) {
+                this.#isSettingNameHack = false;
+                return;
+            }
+
+            // Even if the node does not vary with languages or segments its still gives us one variant
+            const firstVariant = this.#variants[0];
+            if(!firstVariant) {
+                this.#isSettingNameHack = false;
+                return;
+            }
+
+            var umbVariant = new UmbVariantId(firstVariant.culture, firstVariant.segment);
+            this.#docWorkspaceCtx?.setName(currentName + '1', umbVariant);
+            this.#docWorkspaceCtx?.setName(currentName, umbVariant);
+
+        } finally {
+            this.#isSettingNameHack = false;
+        }
+    }
+    // ================================================================================
 }
 
 // Declare a api export, so Extension Registry can initialize this class: