Make use of new GitHub "Issue types" feature

[mhucka]

GitHub recently introduced an "issue types" property. It shows up in the right-hand sidebar on issue pages, like this:

Clicking the type shows a drop-down menu:

The type values can be entirely customized, albeit at the org level and not the individual repo level. The types can be used in projects (e.g., we could add a column in our Cirq roadmap), and can be a field to search and filter issues in the issue list:

The type value seems to be closest to Cirq's kind/* labels. This leads to the following idea:

Why don't we replace the kind/* labels with GitHub Issue types?

[pavoljuhas]

Not sure if it will be wothwhile improvement to the current workflow.

[mhucka]

Discussed at Cirq Cynq 2025-02-05: the consensus is that we have a workflow already established using tags, and switching to the "types" property would involve work (configuring, re-labeling existing issues) without a clear benefit – the project already has a way to express equivalent concepts.

If this changes in the future, we can revisit & reevaluate then.