End of year 2024 repo health check

[ericstj]

A few months have passed since the last repo health survey, so we'd like to reach out and check in on how we are doing.

As before, we'll post the aggregated results when we close the survey. This is an anonymous, 2 question survey. (Also posted in several other repos, each have their own survey so you can answer more than one.)
https://www.surveymonkey.com/r/5CZSDJW

In the past months while also working to get .NET 9.0 out the door, we've invested in a few places in the repository health and infrastructure, including but not limited to:

1. "Merge on green" support to track and categorize known build failures and include dump information on crashes. This should improve PR validation reliability as it helps us track and drive down flaky results rather than relying on rerun.
2. Intermittent errors building CoreCLR on Windows ARM #104674 impacting build reliability and performance on ARM mentioned in the last survey has been fixed.
3. Our api-ready-for-review backlog is clear and help-wanted issues have increased to 533. We still have a lot of api-suggestion issues that could be moved forward and the best way to make this happen is to upvote and collaborate in the discussion to mark as help-wanted or api-ready-for-review. We can't promise that we'll have time to work through the designs in all these cases, sometimes doing so is the biggest part of the work, but please let us know which are most important to you - with your upvotes and participation.

Additionally, I'd like to extend a thanks to our community maintainers in @dotnet/dotnet-runtime-triage who help keep dotnet/runtime running!
@omajid @xoofx @tmds @martincostello @filipnavara @clamp03 @am11 @a74nh @Clockwork-Muse @huoyaoyuan @Sergio0694 @teo-tsirpanis @shushanhf @SingleAccretion