Fix System.Diagnostics.Process tests

[jeffhandley]

There are several tests in System.Diagnostics.Process that don't behave properly and need to be fixed.

• always try to add the result of getegid to the list returned by getgroups #46302
• Fix and reenable TestUserCredentialsPropertiesOnWindows  #46083, ensure test TestUserCredentialsPropertiesOnWindows is run only by elevated accounts #46213, use a different way of removing the access for the temporary test account #46527
• Make StartInfo_TextFile_ShellExecute test more reliable #46133
• try to re-enable GetProcessesByName_ProcessName_ReturnsExpected test  #46140
• Add test for System.Diagnostics.Process.Responding #46142
• disable MainWindow*_GetWithGui_ShouldRefresh_Windows tests for Windows Server Core #46387

Edit
Removed from scope for the 6.0.0 milestone: #13757 (Draft PR: #46292)

[ghost]

Tagging subscribers to this area: @eiriktsarpalis
See info in area-owners.md if you want to be subscribed.

Issue Details

---

There are several tests in System.Diagnostics.Process that don't behave properly and need to be fixed.

• always try to add the result of getegid to the list returned by getgroups #46302
• Fix and reenable TestUserCredentialsPropertiesOnWindows  #46083, ensure test TestUserCredentialsPropertiesOnWindows is run only by elevated accounts #46213, use a different way of removing the access for the temporary test account #46527
• Make StartInfo_TextFile_ShellExecute test more reliable #46133
• try to re-enable GetProcessesByName_ProcessName_ReturnsExpected test  #46140
• Add test for System.Diagnostics.Process.Responding #46142
• disable MainWindow*_GetWithGui_ShouldRefresh_Windows tests for Windows Server Core #46387
• Try to make ProcessNameMatchesScriptName test more reliable #46292

Author:	jeffhandley
Assignees:	-
Labels:	area-System.Diagnostics.Process, untriaged
Milestone:	-