Change IList<string> to IEnumerable<string> in Process Run/StartAndForget methods

[Copilot]

The arguments parameter in Process.Run, RunAsync, RunAndCaptureText, RunAndCaptureTextAsync, and StartAndForget was typed as IList<string> despite the implementation only iterating (never indexing or mutating) the collection. This is inconsistent with the existing Process.Start(string, IEnumerable<string>) overload.

• ref/System.Diagnostics.Process.cs — updated all five affected method signatures from IList<string>? to IEnumerable<string>?
• src/System/Diagnostics/Process.Scenarios.cs — updated matching public signatures and the private CreateStartInfo/CreateStartInfoForCapture helpers; implementation body unchanged (already used foreach)

API approved in #130364 (comment)

[adamsitnik]

@copilot address my feedback

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-diagnostics-process
See info in area-owners.md if you want to be subscribed.

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

This PR updates the public System.Diagnostics.Process “scenario” APIs to accept IEnumerable<string>? for command arguments instead of IList<string>?, aligning with the existing Process.Start(string, IEnumerable<string>) pattern and removing an unnecessary list requirement.

Changes:

• Updated Process.Run, RunAsync, RunAndCaptureText, RunAndCaptureTextAsync, and StartAndForget overloads to take IEnumerable<string>? arguments = null.
• Simplified internal CreateStartInfo* helpers to pass the enumerable directly to new ProcessStartInfo(fileName, arguments) when non-null.
• Updated the ref/ contract accordingly (public API surface change).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File	Description
src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.Scenarios.cs	Updates public overload signatures and internal helper signatures; uses ProcessStartInfo(string, IEnumerable<string>) when arguments are provided.
src/libraries/System.Diagnostics.Process/ref/System.Diagnostics.Process.cs	Updates the public reference surface for the five affected APIs to IEnumerable<string>?.

[adamsitnik]

@copilot address the feedback

[Copilot]

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.Scenarios.cs:68

• This overload can throw ArgumentException when fileName is empty (via ArgumentException.ThrowIfNullOrEmpty(fileName) in CreateStartInfo), but the XML docs only mention the null case. Please document the empty-string exception for consistency with the other fileName overloads in this file.

        /// The command-line arguments to pass to the process. Pass <see langword="null"/> or an empty sequence
        /// to start the process without additional arguments.
        /// </param>
        /// <returns>The process ID of the started process.</returns>
        /// <exception cref="ArgumentNullException"><paramref name="fileName"/> is <see langword="null"/>.</exception>