Diagnostics Repo Engineering Summary

A catch all and list of all the diagnostics repo engineering issues:

- [ ] https://github.com/dotnet/diagnostics/issues/5462
- [ ] Remove netstandard2.0 builds. Build/hosting net47/net8.0.
- [ ] Build/test SOS for the s390x, riscv64 and ppc64le architectures: https://github.com/dotnet/diagnostics/issues/4494
- [ ] Remove managed build/restore from test only legs
- [ ] Sync/merge PAL/UtilCode changes from the latest runtime repo. Add utf16_* library.
- [x] Update System.CommandLine version
- [ ] Investigate why the SOS tests on MacOS take so long (and sometimes time out)
- [x] Add test.cmd/.sh option to just install the test runtimes and run all the tests.
- [x] Drop hosting on and testing against 7.0
- [x] Test against the latest cdb debugger
- [x] https://github.com/dotnet/diagnostics/issues/4421
- [x] Move from building against NET 6.0 to NET 8.0
- [x] Remove hosting/testing NET 6.0
- [x] Test against the .NET 10 runtimes
- [x] Move the symstore repo to diagnostics
- [x] Remove the $(_BuildDisplayName) from build.yml
- [ ] Separate the test portion of build.yml into test.yml if practical
- [ ] Create reliable and tested scripts, etc. to generate test asset dumps for Microsoft.Diagnostics.DebugServices.UnitTests.
- [x] #3882
- [ ] Separate the build legs/steps from the test ones
- [ ] Create our own RemoteExecutor that allows the SDK/runtime to be specified (.dotnet-test in our case)
- [ ] Use `dotnet test` from the .dotnet-test install to run tests on the current SDK and runtimes
- [ ] Remove installing test runtimes in global.json
- [ ] #165
- [x] #3331
- [x] #3326
- [ ] #1942
- [x] #1005
- [x] #1631
- [ ] #1803
- [ ] #3111
- [x] #3551
- [ ] #3552
- [ ] #2865