Update WDIO tests for action menu-based plugin activation

[Copilot]

The eform-angular-frontend now uses an action menu for plugin operations instead of direct toggle buttons. The WDIO tests were still attempting to click non-existent toggle elements, causing test failures.

Changes

• Updated test selectors: Tests now open the action menu (#actionMenu) before interacting with the plugin status button (#plugin-status-button0)
• Added menu lifecycle management: Open menu → perform action → close with Escape key where needed

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

The test flow remains unchanged: verify initial state → activate plugin → verify activated state.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Fix activate plugin after changes to action menu instead of toggle icons directly in frontend</issue_title>
<issue_description>the wdio tests needs to be updated, so the are able to activate the plugin after the changes to https://github.com/microting/eform-angular-frontend/tree/master/eform-client/src/app/modules/plugins-management/components/installed/installed-plugins-page so action menu needs to be opened before activating the plugin</issue_description>

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

• Fixes Fix activate plugin after changes to action menu instead of toggle icons directly in frontend #1166

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.