🔧 Repository: Community Maintainer Owned Plugin Migration from Material UI (MUI) to Backstage UI (BUI)

### 📜 Description

This issue is intended to track migrating the Community Maintainer Owned Plugins from Material UI (MUI) to Backstage UI (BUI)

You can use the Claude MUI to BUI Migration Skill to help you with the migration: https://github.com/backstage/community-plugins/blob/main/.claude/skills/mui-to-bui-migration/SKILL.md

You can find the Backstage UI (BUI) documentation here: https://ui.backstage.io/

You can find example of migrated plugins in the following locations:

- https://github.com/backstage/community-plugins/tree/main/workspaces/announcements
- https://github.com/backstage/community-plugins/tree/main/workspaces/azure-devops/plugins/azure-devops
- https://github.com/backstage/community-plugins/tree/main/workspaces/linguist/plugins/linguist
- https://github.com/backstage/community-plugins/tree/main/workspaces/manage/plugins

The detailed automated migration tracker is here: https://github.com/backstage/community-plugins/issues/7023

> [!WARNING]
> Please create 1 PR per workspace, do NOT submit it as one big change. If you work on this make sure you complete 1 before starting the next, complete means it is approved and merged.

The following workspaces need to be migrated:

- [ ] airbrake
- [ ] allure
- [ ] apache-airflow
- [ ] apollo-explorer
- [ ] badges
- [ ] bazaar
- [ ] cicd-statistics
- [ ] cloudbuild
- [ ] code-climate
- [ ] codescene
- [ ] dynatrace
- [ ] entity-validation
- [ ] firehydrant
- [ ] gcalendar
- [ ] gcp-projects
- [ ] github
- [ ] gitops-profiles
- [ ] gocd
- [ ] grafana
- [ ] graphiql
- [ ] graphql-voyager
- [ ] ilert
- [ ] jaeger
- [ ] jenkins
- [ ] lighthouse
- [ ] linkerd
- [ ] microsoft-calendar
- [ ] newrelic
- [ ] nomad
- [ ] opencost
- [ ] periskop
- [ ] puppetdb
- [ ] sentry
- [ ] shortcuts
- [ ] splunk
- [ ] stack-overflow
- [ ] stackstorm
- [ ] tech-radar
- [ ] todo
- [ ] vault
- [ ] xcmetrics

### 👍 Expected behavior

Community Maintainer Owned Plugins are migrated to Backstage UI (BUI)

### 👎 Current Behavior

Community Maintainer Owned Plugins are using Material UI (BUI) still

### 👟 Reproduction steps

N/A

### 📃 Provide the context for the Bug.

This is a large migration that will enable the improved experience that comes from Backstage UI (BUI)

### 👀 Have you spent some time to check if this bug has been raised before?

- [x] I checked and didn't find similar issue

### 🏢 Have you read the Code of Conduct?

- [x] I have read the [Code of Conduct](https://github.com/backstage/community-plugins/blob/main/CODE_OF_CONDUCT.md)

### Are you willing to submit PR?

No, but I'm happy to collaborate on a PR with someone else

Read .claude/skills/mui-to-bui-migration/SKILL.md and the migration tracker in issue 7023 first, then choose one listed workspace. Compare its existing UI with the migrated examples in workspaces/announcements, workspaces/azure-devops/plugins/azure-devops, workspaces/linguist/plugins/linguist, or workspaces/manage/plugins. Done means one workspace is migrated, its checkbox can be completed, and the PR is approved and merged before starting another.

Written by the indexing model from the issue text.