[meta] Use new issue types for bugs and feature requests

[FichteFoll]

Instead of the "T: bug", "T: enhancement" and "T: feature" labels, we could use the new "Type" field for github issues.

In this task, we would

• Create the "Enhancement" and "Discussion" types. Must be done by an administrator via https://github.com/organizations/sublimehq/settings/issue-types.
• Set the type of all tickets with one of the three labels using batch operations based on filters.
• Adjust github templates to set the type instead of the label. Compare https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax
• Remove the old labels.

Open question: Do we still need to differentiate between a feature and an enhancement request or is the "significant" label sufficient?

[jrappen]

Also, only organization owners can edit issue types via the organization settings. This might be an issue as I don't see Jon or Ben doing that.

It would make sense to make a list with types and type descriptions first, as org owners have to set them.

[FichteFoll]

Added a todo item to create the only missing "Enhancement" type and I also suggest to create a "Discussion" type for the tickets currently labeled with "RFC". They could arguably also be converted to actual discussions, but that can be done at a later point in time.

[jrappen]

@FichteFoll type can be set in templates now. Added a reference link to the docs to the opening comment.

[jrappen]

@FichteFoll I added a link to your opening comment as to where adjust the settings directly.

[jrappen]

What about "Core Bug", which is currently a label? I assume it should stay that way, as types are org-wide and the "Core Bug" label is only used in this repo.

[FichteFoll]

Indeed, that should remain as an informative label. The underlying type is still a bug, but it's not something that can be addressed here, so it's closer to "wrong repo" but softer.