Get rid of the "untriaged" auto-label on Github issues

[willdean]

The dotnet/sdk Github repo auto-labels all new issues as "untriaged".

But there doesn't actually appear to be any systematic triage process for Github issues, which means that we now have roughly 40% (>1000) of all open issues marked as "untriaged", going back years and years.

To me this creates an appearance of neglect/abandonment which, whether it's true or not, cannot really align with MS' marketing objectives. Additionally it's vaguely insulting to external contributors who might feel that, if nothing else, they deserve to have issues reviewed in some way. (This is not a personal complaint!)

I recognise that actually triaging every issue is very expensive - but there's no point putting a label on which implies it's being done if it isn't. Getting rid of the label would not be expensive.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[marcpopMSFT]

I appreciate your feedback here and admit that we fell behind on following up on the untriaged issues. The label was added a few years ago to help us track incoming both between our team and the other teams that contribute to this repo as well as to enable everyone on the team to contribute to triage as it was too large a set to manage in a meeting.

We're now better staffed on the SDK team and generally staying more on top of recent incoming. We've started doing a pass over old issues using the untriaged label as a guide for that. It will take some time but using that method, we plan to catch up over the coming months and I intent to continue to use this label for now. If we aren't able to catch up, we'll revisit and see if there's another approach.