Plugin E2E: Select MultiSelect options sequentially

[mckn]

What this PR does / why we need it:

Replaces Promise.all(values.map(...)) with a sequential for...of loop in MultiSelect.selectOptions. Playwright interactions on the same UI element are not safe to run concurrently — racing clicks against the same open menu can cause flaky tests because the DOM mutates after each selection. The sequential approach ensures each option is fully selected before the next begins.

Which issue(s) this PR fixes:

Fixes a potential source of flaky tests flagged in #2621 (comment)

Special notes for your reviewer:

The behavior is unchanged — same options are selected in the same order, just awaited one at a time instead of concurrently.

📦 Published PR as canary version: Canary Versions

✨ Test out this PR locally via:

npm install @grafana/plugin-e2e@3.7.2-canary.2626.25732312320.0
npm install @grafana/sign-plugin@3.2.2-canary.2626.25732312320.0
# or 
yarn add @grafana/plugin-e2e@3.7.2-canary.2626.25732312320.0
yarn add @grafana/sign-plugin@3.2.2-canary.2626.25732312320.0

[cla-assistant]

All committers have signed the CLA.

[Copilot]

Pull request overview

This PR reduces flakiness in @grafana/plugin-e2e component interactions by making MultiSelect.selectOptions select values sequentially instead of concurrently, avoiding Playwright races against the same open menu element.

Changes:

• Replaced concurrent Promise.all(values.map(...)) selection with a sequential for...of loop.
• Preserved the API contract by still returning the selected option text values as a string[].

[github-actions]

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged and will trigger a new patch release.
NOTE: When merging a PR with the release label please avoid merging another PR. For further information see here.

[sunker]

LGTM

[github-actions]

Playwright test results

Image Name	Version	Result	Report
grafana-enterprise	nightly	✅
grafana-enterprise	dev-preview-react19	✅
grafana-enterprise	13.0.1	✅
grafana-enterprise	12.1.10	✅
grafana-enterprise	11.0.11	✅
grafana-enterprise	9.3.16	✅
grafana-enterprise	8.5.27	✅

Troubleshooting

404 when clicking on View report

By default, the deploy-report-pages Action deploys reports to the gh-pages branch. However, you need to take an extra step to ensure that GitHub Pages can build and serve the site from this branch. To do so:

1. Go to the Settings tab of your repository.
2. In the left-hand sidebar, click on Pages.
3. Under Source, select Deploy from a branch, then choose the gh-pages branch.

This action needs to be completed manually in order for your GitHub Pages site to be built and accessible from the gh-pages branch. Once configured, GitHub will automatically build and serve the site whenever new reports are deployed.

[grafana-plugins-platform-bot]

🚀 PR was released in @grafana/plugin-e2e@3.7.2, @grafana/sign-plugin@3.2.2 🚀