Plugin E2E: Bump @grafana/e2e-selectors to 13.0.0-22149689148

[grafana-plugins-platform-bot]

Automated update of @grafana/e2e-selectors to version 13.0.0-22149689148.

Triggered by grafana/grafana when changes were detected in the e2e-selectors package.

📦 Published PR as canary version: Canary Versions

✨ Test out this PR locally via:

npm install @grafana/plugin-docs-cli@0.0.3-canary.2466.22151407209.0
npm install @grafana/plugin-docs-parser@0.0.2-canary.2466.22151407209.0
npm install @grafana/plugin-e2e@3.3.3-canary.2466.22151407209.0
# or 
yarn add @grafana/plugin-docs-cli@0.0.3-canary.2466.22151407209.0
yarn add @grafana/plugin-docs-parser@0.0.2-canary.2466.22151407209.0
yarn add @grafana/plugin-e2e@3.3.3-canary.2466.22151407209.0

[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	12.4.0-22148923374	✅
grafana-enterprise	12.3.3	✅
grafana-enterprise	11.6.11	✅
grafana-enterprise	10.4.19	✅
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.

[hugohaggmark]

Oops, maybe we should wait with this