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: - ~Bug - ~Documentation - ~Feature - ~Task - ~UX (arguably, see below) ~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](https://gitlab.tails.boum.org/groups/tails/-/issues?sort=created_date&state=opened&label_name%5B%5D=UX%3Adebt) to track the concept of "[UX debt](https://www.nngroup.com/articles/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`. With that said, the first iteration of scoped `type::` labels could include: - `Type::Bug` - `Type::Documentation` - `Type::Enhancement` - `Type::Feature` - `Type::Task` - `Type::UX Debt` However I'm sure others will have ideas for additional issue types too.

issue