chore: sync repo with latest npm releases

[jackw]

What this PR does / why we need it:
The latest mandatory zizmor checks brownout caused the publishing pipeline to fail to push commits to main which also prevented the gh releases from being created. This has the unfortunate side-effect of preventing packages in this repo from being published now as the version calculation doesn't take into account the last published packages. This PR addresses the first part of the issue by adding the changes auto would have pushed to the repo. I will manually create the associated gh releases once this PR is approved.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

[Copilot]

Pull Request Overview

This PR synchronizes the repository with pending npm releases by manually applying version bumps and changelog entries that the automated publishing pipeline failed to commit due to a zizmor checks brownout. The changes prepare the repository for manual GitHub release creation.

Key Changes:

• Version bumps for three packages affected by the publishing failure
• Addition of changelog entries documenting the previously published bug fix

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/plugin-e2e/package.json	Bump version from 2.2.1 to 2.2.2
packages/create-plugin/package.json	Bump version from 6.1.0 to 6.1.1
packages/create-plugin/CHANGELOG.md	Add v6.1.1 changelog entry for install command fix
docusaurus/website/package.json	Bump version from 4.0.1 to 4.0.2
CHANGELOG.md	Add root-level changelog entry for the bug fix release

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[github-actions]

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

✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs.

[github-actions]

Playwright test results

Image Name	Version	Result	Report
grafana-dev	12.3.0-18685446948	✅
grafana-enterprise	12.2.1	✅
grafana-enterprise	11.5.10	✅
grafana-enterprise	10.3.12	✅
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.