Automatically label issues and prs with plugin labels

[snejus]

Add GitHub issue and PR auto-labeler workflow

Introduces automated label triage for issues and PRs using the github/issue-labeler action.

What changed:

• .github/labeler.yaml — defines regex patterns mapping ~80 plugin names to their corresponding labels. Ambiguous short names (e.g. convert, edit, play) require either a plugin suffix or a <name>: prefix in the title to avoid false positives.
• .github/workflows/label-issues.yaml — triggers on issue/PR open and edit events, matches against the title only (not the body), and syncs labels so stale ones are removed on edits.

Impact: Zero runtime cost; purely a CI/triage quality-of-life improvement. Makes it easier to filter and route plugin-specific issues without manual labelling.

[Copilot]

Pull request overview

PR add GitHub Actions workflow to auto-label issues + PRs from title, using github/issue-labeler and a big regex map of plugin names to labels.

Changes:

• Add .github/workflows/label-issues.yaml to run labeler on issue/PR open + edit, title-only, and sync labels.
• Add .github/labeler.yaml with regex patterns for many plugin-name labels (some with extra disambiguation rules).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
.github/workflows/label-issues.yaml	New workflow to run github/issue-labeler on issues + PRs and keep labels in sync.
.github/labeler.yaml	New label-to-regex config mapping plugin names to label matches.

[JOJ0]

Very nice feature! For the "Plugins' Kanban Board" it would be nice if the one required tag could also be added. It's named plugins, but I suppose this is not possible without manually maintaining a list of things/words that are plugins. But for now this LGTM and we can think about this feature request later.

PS: I am too lazy to test this in my fork ATM. Or I can do that quickly if you think it helps? How?

[snejus]

It needs to be merged in order to be tested! Let's see