Proposal: Use scoped labels to categorize issue type

I think that it would be helpful to scope the labels we use to categorize issue type, so that each issue belongs to a single type.

Some existing examples of issue types are:

UX was originally intended to be used to summon the UX Team, but now gets used somewhat randomly to tag issues affecting the user experience. If we decide to keep this label, I think we should provide a clearer scope for its use. For instance, the Tails Team use a UX:debt label on their GitLab instance to track the concept of "UX debt". I would advocate in favor of adopting the same change.

I imagine a similar argument could be made for a "Technical debt" label too. Perhaps it could even be argued that these should be distinct from a scoped type:: label, given the potential overlap with Type::Enhancement.

Proposed schema

new label replaces description
Kind::Bug Bug A defect where existing functionality fails to work as intended, including crashes, errors, and regressions.
Kind::Enhancement N/A An improvement to existing functionality that makes it better, faster, or more usable.
Kind::Feature Feature A new capability or piece of functionality that does not exist yet.
Kind::Technical Debt Technical Debt Outdated or poorly structured code, dependencies, or infrastructure in need of refactoring.
Kind::Documentation Documentation A gap, error, or needed improvement in our documentation.
Kind::Chore Task Routine housekeeping that keeps the team and tooling running but doesn't change the product — such as dependency updates, release steps, or admin tasks.
Edited by donuts