Update WDIO tests for action menu-based plugin activation

[Copilot]

The eform-angular-frontend now uses action menus for plugin operations instead of direct toggle buttons. Tests were attempting to click non-existent elements.

Changes

• Import: Added $ from '@wdio/globals' for direct element selection
• Status verification: Tests now open action menu (#action-items-0 → #actionMenu), query status button (#plugin-status-button0), and read status from mat-icon text content
• Activation flow: Open menu → click status button → confirm modal → wait for initialization → re-login → verify via menu
• Menu lifecycle: Added proper open/close with Escape key and appropriate waits

Example

// Before: Direct interaction (no longer works)
const plugin = await pluginPage.getFirstPluginRowObj();
await plugin.enableOrDisablePlugin();
expect(plugin.status).eq('toggle_on');

// After: Action menu interaction
const actionMenuBtn = await $('#action-items-0').$('#actionMenu');
await actionMenuBtn.click();
await browser.pause(500);

const statusBtn = await $('#plugin-status-button0');
await statusBtn.click(); // Activates plugin

const statusIcon = await statusBtn.$('mat-icon');
expect(await statusIcon.getText()).eq('toggle_on');

Follows pattern from workflow-plugin#1167.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Update WDIO tests for action menu-based plugin activation</issue_title>
<issue_description>Use microting/eform-angular-workflow-plugin#1167 as reference to what needs to be done</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Update WDIO tests for action menu-based plugin activation #1182

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.