Labels for issues and PRs

[altrisi]

I'd like to propose labelling issues and PRs in this repo to organize them, since all are currently unlabelled.

Proposals for the names for each of them are encouraged here. Github finally released the built-in vote up/down, so no need to use reactions to vote.

It wouldn't be a 100% of the time, first thing to do: Label the thing, but add it if willing to/having a second. Also a way for me to ask you for what to use for non-standard cases that may still be nice to see from outside of the issue/PR, with you knowing what's going on.

@BisUmTo @Ghoulboy78 @replaceitem (did I miss any collaborator?/should I ping gnembon for this?)
Sorry for the pings if you didn't want to be pinged.

[altrisi]

• Bug: bug (built-in, red)
• Enhancement: enhancement (built-in, aqua)
• Questions about apps here or Scarpet support: question (built-in, pink)
• Refactor of an app: refactor (let github choose the color, or suggest one)
• Addition of new app: new-app (let github choose the color, or suggest one)
• Updating of an app: app-update (and tech-debt if something was broken) (let github choose the color, or suggest one)
• Adding functionality to an app: update + enhancement
• Deprecated functions: tech-debt (let github choose the color, or suggest one) (inspired by WE's one)
• Documentation: documentation (let github choose the color, or suggest one)
• On hold: on-hold (gray-ish) (this would be for PRs like Update camera.sc compared to Fabric Carpet (alternative to #187) #188 that are waiting for either an update of the app in another repo, an addition to the language, or a release of in development Scarpet features. Maybe adding extra waiting-for-release and requires-carpet-pr?)
• Proposal to add something to the Scarpet language: invalid (built-in, white) (since those should be in gnembon/fabric-carpet)
  Same for general Scarpet bugs