Bottles' GitHub labels rework

[Qronikarz]

@TheEvilSkeleton Mentioning you here because of my previous post.

Current labels: https://github.com/bottlesdevs/Bottles/labels

Changes:

• Backend rewrite -> zz backend rewrite (move it to the end of the list since it's not needed now?)
• blocked -> Status: Blocked
• Bug -> Type: Bug
• Can't replicate -> Status: Can't replicate
• Concept -> Type: Concept (use it on discussions)
• Crash -> Type: Crash
• dependencies -> Type: Dependency
• Duplicate -> Type: Duplicate
• Enhancement -> Type: Enhancement
• experimental -> zz experimental (I don't feel like it's needed now)
• Feature request -> Type: Feature Request (also could be converted into discussion in "ideas" category, but it still needs to be tagged.
• Feedback -> Type: Feedback (can be also converted into discussions)
• Good first issue -> Status: Good first issue (I don't know if this one can be renamed since it's used by GitHub to show on repositories that "X issues need help")
• help wanted -> Status: Help wanted
• Hotfix -> zz hotfix (used only once)
• Infrastructure -> Type: Infrastructure
• Invalid -> Type: Invalid
• Need to Investigate -> Status: Needs investigating
• Not a bug -> Type: Not a bug
• Offtopic -> Type: Offtopic
• Poll -> Type: Poll
• Requires evaluation -> zz requires evaluation (there already is Status: Needs investigating label. For me those are synonyms, but if not then rename it into Status: Requires evaluation)
• Task -> zz task (most of the issues are tasks, I don't understand this label)
• To be merged for next release -> Status: To be merged for next release
• Translations -> Type: Translations
• Unsupported Package -> Type: Unsupported package
• Waiting response -> Status: Waiting for response
• WIP -> Status: WIP
• Wontfix -> Status: Wontfix (alternatively, type: wontfix, but I feel like it's more of a status)

Additions:

• Priority: Critical (color: red) - issue that requires immediate or as quick as possible resolving. Example: [Bug]: Unable to update runners and create bottles #2704
• Priority: High (color: orange) - pretty important issue that should be worked before the next release if possible
• Priority: Medium (color: yellow) -
• Priority: Low (color: green) - issue that doesn't really need fixing any time soon, but still nice to fix in the future: Shadow on bottles screen with no bottles #2696
• Type: Bottles next (color: purple?) - issue that isn't applicable to current version of Bottles and needs to be implemented in Bottles Next (or whatever it ends up being called). Ideally also move it to Bottles Next issue tracker. Example: Integrate UMU-Launcher for a Native-Like Windows Gaming Experience #3537
• Status: Waiting upstream - issue with a library or component that Bottle uses and Bottles fix/implement it by itself. Example: Add UWP/WinRT support. #672
• Type: UI - issue that deals with the User Interface of Bottles. Example: Shadow on bottles screen with no bottles #2696
• Type: Library - issue that deals with the library part of Bottles. Example: [Request]: Library - count hours played #1273
• Type: Packaging - issue that deals with Bottles packaging. Yes, I know only flatpak is currently supported, but maybe in the future there will be more packages - nix, appimage, flatpak, cpak, snap etc. Example: Bottles AppImage #1272
• Status: Wontadd - wontfix but for feature requests/program requests. Example: [Request] Support Lutris scripts #1149
• Status: Completed - issue that succesfuly was fixed or implemented. Example: Move to GTK4 and libadwaita #610
• Status: Autoclosed stale - issue that got autoclosed by the bot due to time inactivity. You already know my opinion, but if it needs to stay, the issues should get tagged so they can be visibily different from issues closed normally. Example: [Request] Notify runner updates #333

Probably forgot about few (of course I did), but they can be added later if needed.

[TheEvilSkeleton]

Thanks a lot for your effort, and sorry for replying two weeks later... Are you reachable somewhere (Matrix or Discord)? It's difficult to keep track of GitHub notifications and emails

[Qronikarz]

Don't worry.

Discord is a no.
As for matrix I've been meaning to try it, but I haven't gotten around to it yet. Though it feels like it's better now than later since increasingly more projects do use it. I'm going to research about what server to pick.