Add feature / balance request triaging for Github Issues

[SlamBamActionman]

This PR includes a change to the Triaging Procedure to give more freedom for Triagers to close feature and balance requests in Github Issues.

In short; we have 3.7k issues and a fair number of them are feature or balance requests. Ideally Github Issues should be a place Contributors can easily pick up things to work on without worry, and having requests that will result in closed PRs or long lead times isn't respectful to either Contributors or Maintainers.

It's better that these discussions happen on Discord or on the Forums, rather than Github Issues.

[K-Dynamic]

What's the problem with labelling issues as feature requests and using the filter?

I've made a couple of feature requests on Discourse but it doesn't really get as much traction as Github.

[SlamBamActionman]

What's the problem with labelling issues as feature requests and using the filter?

I've made a couple of feature requests on Discourse but it doesn't really get as much traction as Github.

I think it is better for Github Issues to be "actionable". I.e. a Contributor should be able to open a Github Issue and resolve it, whether that be through implementing a PR or replicating a bug.

We already have Discord and the Forums for feature pitches. Encouraging Maintainers to be more proactive with creating S: Conceptually Approved-labeled issues from this is something we should aim for.

[murphyneko]

Thank you 🙏