feat: plugins-e2e pre-navigate hook

[shelldandy]

This PR helps fixtures enhance the navigate method by adding any sort of logic before the ctx.page.goto() call use cases can be:

• Ensuring grafana menus are closed before anything else happens for consistent screenshot testing
• Setting up localStorage variables needed for all tests of an app

📦 Published PR as canary version: Canary Versions

✨ Test out this PR locally via:

npm install [email protected]
npm install @grafana/[email protected]
npm install @grafana/[email protected]
npm install @grafana/[email protected]
# or 
yarn add [email protected]
yarn add @grafana/[email protected]
yarn add @grafana/[email protected]
yarn add @grafana/[email protected]

[github-actions]

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

✨ This PR can be merged and will trigger a new minor 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.0.0-238150	✅
grafana-enterprise	11.6.0	✅
grafana-enterprise	11.3.5	✅
grafana-enterprise	10.2.9	✅
grafana-enterprise	9.2.20	✅
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.