Label suggestions

[mfisher87]

I think we can make our labels a bit more clear by making them multi-part with a delimiter (: or /). Many other projects do this, e.g. matplotlib. I don't have other great examples off the top of my head. What other projects are absolutely rocking the labels?

To start with, I propose:

• automation CI, CD, or other automation -> impact/automation
• bug Something isn't working -> type/bug
• dependencies Pull requests that update a dependency file -> impact/dependencies
• documentation Improvements or additions to documentation -> impact/documentation
• duplicate This issue or pull request already exists -> type/duplicate
• enhancement New feature or request -> type/enhancement
• feedback requested We requested feedback from the reporter; if we don't hear back in X days the issue may be closed -> needs/feedback
• github_actions Pull requests that update GitHub Actions code -> remove, we have the impact/automation label for this
• good first issue Good for newcomers -> keep as-is, this is a special label we want to optimize for searchability
• hackathon An issue we'd like to visit during a hackathon event -> ?
• help wanted Extra attention is needed -> needs/help
• invalid This doesn't seem right -> remove? unused.
• python Pull requests that update Python code -> remove? unused. or: impact/library. Or impact/core in preparation for a future impact/plugin label.
• question A question needs to be answered to proceed -> remove? Should use GitHub discussions?
• wontfix This will not be worked on -> type/will-not-do (using a contraction in a label without spacing is really hard to read even as a native English speaker - we can be more inclusive :) )

#281 offers us a mechanism to automatically apply these labels as issues are created. It also offers a mechanism to remove or avoid some labels by directing users away from Issues and towards a more appropriate place, e.g. type/feature-request need not exist as a "request" should (IMO :) ) start in Discussions and only become an issue once we agree it is a feature we will implement. Same for type/question.

I also propose colorizing the items based on the group they're in!