[BUG]: Overwriting a workspace action removes popover menu items

[warrenbuckley]

Describe the bug I expect to overwrite just a single Workspace Action without having to copy & reimplement all the child menu workspace actions.

To Reproduce Steps to reproduce the behavior:

• Implement an overwrite of a workspace action
• Ensure you overwrite a workspace action that had child popover menu items
• Once overwritten you will see the split menu button no longer appears and the child menu items are not available.

import { UMB_ENTITY_IS_NOT_TRASHED_CONDITION_ALIAS } from '@umbraco-cms/backoffice/recycle-bin';
import type { ManifestWorkspaceActions } from '@umbraco-cms/backoffice/extension-registry';

export const manifests: Array<ManifestWorkspaceActions> = [
{
        type: 'workspaceAction',
        kind: 'default',
        overwrites: 'Umb.WorkspaceAction.Document.SaveAndPublish', // Alias of thing you wanna overwrite
        alias: 'Custom.WorkspaceAction.Document.SaveAndPublish',
        name: '[Custom] Save And Publish Document Workspace Action',
        api: () => import('./custom.save-and-publish.action.js'),
        weight: 70,
        meta: {
            look: 'primary',
            color: 'positive',
            label: 'My custom Save & Publish',
        },
        conditions: [
            {
                alias: 'Umb.Condition.WorkspaceAlias',
                match: 'Umb.Workspace.Document',  // Cant get UMB_DOCUMENT_WORKSPACE_ALIAS const
            },
            {
                alias: UMB_ENTITY_IS_NOT_TRASHED_CONDITION_ALIAS,
            },
        ]
    },  
];

Expected behavior I expect to overwrite just a single Workspace Action without having to copy & reimplement all the child menu workspace actions.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS] Windows 11
• Browser [e.g. chrome, safari] Edge
• Version [e.g. 22] 126.0.2592.68 (Official build) (64-bit)

[github-actions[bot]]

Hi there @warrenbuckley!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face: