fix: Adding Subnetwork to a configuration without a Communication Element failed for the first time

When creating a `Communication` Element in Communication.ts, the created Element is also returned to use it as a parent for the wizard

The `Should create a Communication Element` integration test is extended to also check that the Wizard is closed properly

Signed-off-by: Pascal Wilbrink <[email protected]>

Author: pascalwilbrink

test/integration/editors/communication/Communication.test.ts

@@ -86,8 +86,6 @@ describe('Communication Plugin', () => {
           await fab.click();
           await new Promise(resolve => setTimeout(resolve, 100)); // await animation
           await parent.updateComplete;
-
-          expect(parent.wizardUI.dialogs.length).to.equal(1);
 
           const dialog: Dialog = parent.wizardUI.dialog!;
           expect(dialog).to.not.be.undefined;