PluginE2E: Move away from networkIdle

[jackw]

What this PR does / why we need it:

The last 2 minor releases of playwright have caused multiple issues (#1606 , #1728 , #1740 , #1741) with plugin-e2e due to changes with using chromiums headless browser and workers picking up events in different ways. This is mainly surfaced with timeouts due to networkIdle being used across all the plugin-e2e page models to wait for a page to load when navigating.

This PR switches networkIdle out for load (which is the default), fixes up any of the issues we can easily identify from the tests in this repo, and continues to allow developers to set the waitUntil property as they see fit.

Once we're confident these tests are not flakey we'll move on to testing a canary build of plugin-e2e in Grafana before merging.

Which issue(s) this PR fixes:

Fixes #1734
Fixes #1745

Special notes for your reviewer:

📦 Published PR as canary version: Canary Versions

✨ Test out this PR locally via:

npm install @grafana/plugin-e2e@2.0.0-canary.1746.14835096080.0
# or 
yarn add @grafana/plugin-e2e@2.0.0-canary.1746.14835096080.0

[github-actions]

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

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

[andresmgot]

LGTM, a couple of nits

[github-actions]

Playwright test results

Image Name	Version	Result	Report
grafana-dev	12.1.0-241686	✅
grafana-enterprise	11.6.1	✅
grafana-enterprise	11.3.6	✅
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.

[grafana-plugins-platform-bot]

🚀 PR was released in @grafana/plugin-e2e@2.0.0 🚀