chore: fix up failed releases [skip-ci]

[jackw]

What this PR does / why we need it:
Clean up for packages that were published to NPM but new GH org ruleset prevented bot from pushing to main.

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. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs.

[Copilot]

Pull request overview

This PR performs a release cleanup by bumping package versions and updating changelogs after a publish occurred but automated pushes to main were blocked by new GitHub org rules.

Changes:

• Bump @grafana/plugin-e2e from 3.7.0 → 3.7.1 and add the v3.7.1 changelog entry.
• Bump @grafana/create-plugin from 7.3.0 → 7.3.1 and add the v7.3.1 changelog entry.
• Update root CHANGELOG.md (new release section + minor formatting/escaping tweaks).

Reviewed changes

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

Show a summary per file

File	Description
packages/plugin-e2e/package.json	Version bump to 3.7.1.
packages/plugin-e2e/CHANGELOG.md	Adds v3.7.1 release notes.
packages/create-plugin/package.json	Version bump to 7.3.1.
packages/create-plugin/CHANGELOG.md	Adds v7.3.1 release notes + escaping fix in older entry.
CHANGELOG.md	Adds release summary for the bumped packages + minor formatting tweak.

[github-actions]

Playwright test results

Image Name	Version	Result	Report
grafana-enterprise	nightly	✅
grafana-enterprise	dev-preview-react19	✅
grafana-enterprise	13.0.1	✅
grafana-enterprise	12.1.10	✅
grafana-enterprise	11.0.11	✅
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.