New edit content experience not launched from UVE for content types that should use the new edit content

[MariaFernandez778]

Problem Statement

When the new edit content experience is enabled for a content type, it is expected to be shown consistently whenever and wherever that content type is accessed.

Currently, when you enable the new editor and try to access it via the UVE (Universal Visual Editor), clicking "Go to Full Editor" does not launch the new experience. Instead, it redirects the user to the old editor, navigating them away from their current context.

Steps to Reproduce

1. Enable new edit content for a specific content type.
2. Attempt to open said content type from the UVE.
3. Click on "Go to Full Editor".
4. Observation: The old edit content is shown, and the user is navigated out of the UVE context.

Implementation Details

To resolve this and improve the UX, the editor should open in a fullscreen dialog to keep the user in context:

• Reuse DotEditContentDialogComponent via PrimeNG's DialogService.

Additionally, the same routing logic is applied to two other entry points within the UVE where new content can be created:

• Dragging a content type from the palette onto the page
• Clicking the "+" button inside the content type selector dialog (ng-contentlet-selector)

Also about the Dialog Close Behavior

• The edit content dialog must include a "Close" button in the footer
• Closing the dialog via the Close button, the X icon, or the ESC key while there are unsaved changes must display a
  confirmation prompt with two options:
  • Keep Editing — dismisses the prompt and returns the user to the editor
  • Discard Changes — closes the dialog without saving

Cases

1- Hover on a content type and select Edit (pencil icon)

2- Click on Quick edit (Lightning bolt icon) and then "Edit in full editor"

3- Drag and drop any content with the new edit content enabled

4- Click the + button and select the content type

Acceptance Criteria

• AC1: Clicking "Edit in Full Editor" and "Edit" after hover a content type opens the content editor in a fullscreen dialog when the content type has the new content editor enabled.
• AC2: The dialog uses DotEditContentDialogComponent with closable: true and closeOnEscape: true.
• AC3: The editor loads the correct contentlet with no stale field values.
• AC4: Closing the dialog returns the user to UVE with no navigation side effects.
• AC5: When the new content editor is not enabled, the existing behavior remains unchanged.
• AC6: Dragging a content type from the UVE palette onto the page opens DotEditContentDialogComponent in create mode (mode: 'new') when the content type has the new editor enabled. On save, the new contentlet is inserted into the target container.
• AC7: Clicking "+" inside the content type selector dialog opens DotEditContentDialogComponent in create mode when the new editor is enabled. The legacy selector dialog closes before the new one opens. On save, the contentlet is inserted into the target container.
• AC8: When the new editor is not enabled, drag-and-drop and the "+" button in the selector continue using the existing legacy behavior.
• AC10: The edit content dialog must display a Close button in the footer.
• AC11 : When the user attempts to close the dialog (via the Close button, the X icon, or ESC) with unsaved changes, a
  confirmation prompt must appear with Keep Editing and Discard Changes options — Keep Editing returns the user to the
  editor, Discard Changes closes the dialog.

dotCMS Version

Evergreen

Severity

Low - Minor issue or cosmetic