Plugin E2E: Bump e2e selectors

[sunker]

• bump and handle backwards compat
• temp set limit

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

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

[github-actions]

Playwright test results

Image Name	Version	Result	Report
grafana	dev-preview-react19	✅
grafana-dev	13.1.0-24457418213	✅
grafana-enterprise	13.0.0	❌	View report
grafana-enterprise	12.4.3	✅
grafana-enterprise	12.3.6	✅
grafana-enterprise	12.2.8	✅
grafana-enterprise	12.1.10	✅
grafana-enterprise	12.0.10	✅
grafana-enterprise	11.6.14	✅
grafana-enterprise	11.5.10	✅
grafana-enterprise	11.4.8	✅
grafana-enterprise	11.3.9	✅
grafana-enterprise	11.2.10	✅
grafana-enterprise	11.1.13	✅
grafana-enterprise	11.0.11	✅
grafana-enterprise	10.4.19	✅
grafana-enterprise	10.3.12	✅
grafana-enterprise	10.2.9	✅
grafana-enterprise	10.1.10	✅
grafana-enterprise	10.0.13	❌	View report
grafana-enterprise	9.5.21	❌	View report
grafana-enterprise	9.4.17	✅
grafana-enterprise	9.3.16	✅
grafana-enterprise	9.2.20	✅
grafana-enterprise	9.1.8	✅
grafana-enterprise	9.0.8	✅
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.