chore: migrate codeowners to @grafana/grafana-catalog

[tolzhabayev]

Summary

Migrate ownership from the three retiring plugins-platform handles to a single new handle @grafana/grafana-catalog:

• @grafana/plugins-platform → @grafana/grafana-catalog
• @grafana/plugins-platform-frontend → @grafana/grafana-catalog
• @grafana/plugins-platform-backend → @grafana/grafana-catalog

Tracking issue: grafana/grafana-catalog-team#870

Test plan

• CI passes
• CODEOWNERS validation succeeds

[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

Migrates CODEOWNERS entries away from the retiring @grafana/plugins-platform-* teams to the new consolidated owner handle @grafana/grafana-catalog, ensuring ownership routing for key packages and workflows reflects the updated team structure.

Changes:

• Reassign CODEOWNERS for several packages from @grafana/plugins-platform-frontend to @grafana/grafana-catalog.
• Reassign CODEOWNERS for Playwright CI workflow files to @grafana/grafana-catalog.

[tolzhabayev]

Good catch — verified both. Expanded this PR to also update .github/renovate.json reviewer and packages/plugin-e2e/CONTRIBUTING.md tag instruction. PR description scope still reads "ownership migration" since the additions are within that scope.

Did a parallel sweep across the rest of the migration's repos for similar non-CODEOWNERS references — followed up:

• grafana/grafana PR #124469: added .github/renovate.json5 reviewer + 13 modowners-style codeowner annotations in go.mod / pkg/build/go.mod
• grafana/grafana-catalog-team PR README: Update package list #872: updated docs (CLAUDE.md, README.md, two squad docs)
• grafana/grafana PR #124474 (new, docs-only): breaking-changes-guide.md and scripts/modowners/README.md

GitHub App (grafana-plugins-platform-bot[bot]) and Go module path (github.com/grafana/plugins-platform-provisioned) refs are out of scope — those are separate identities from the team handle.

[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.