Update WDIO tests for action menu-based plugin activation

[Copilot]

The eform-angular-frontend changed plugin activation from direct toggle buttons to an action menu interface. The WDIO tests were attempting to click non-existent toggle elements, causing failures.

Changes

• Updated plugin status verification: Tests now open the action menu (#actionMenu) to access the status button, read the mat-icon text for status, and close the menu with Escape
• Updated plugin activation flow: Tests open the menu, click the status button (#plugin-status-button0), confirm in the modal (#pluginOKBtn), wait for setup, then re-login to verify

Example

// Before: Direct interaction (no longer works)
const plugin = await pluginPage.getFirstPluginRowObj();
await plugin.enableOrDisablePlugin();

// 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();

Reference: microting/eform-angular-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 #1855

---

💡 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.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}