Add validation for command-line arguments related to new dotnet test

[Youssef1313]

• Adding validation to command-line options that are mutually exclusive.
• Cleans up the logic around architecture

Pull Request Overview

This pull request introduces command‑line validation for mutually exclusive options and refactors the handling of build options in the dotnet test commands. Key changes include:

• Adding a new ValidateMutuallyExclusiveOptions method in the ValidationUtility class.
• Refactoring TestApplication and related classes to use a BuildOptions instance instead of a List of arguments.
• Updating MSBuildHandler and TestModulesFilterHandler methods to align with the new BuildOptions usage.

Reviewed Changes

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

Show a summary per file

File	Description
src/Cli/dotnet/commands/dotnet-test/ValidationUtility.cs	Introduces mutually exclusive options validation logic.
src/Cli/dotnet/commands/dotnet-test/TestApplication.cs	Replaces _args with BuildOptions and adjusts argument construction logic.
src/Cli/dotnet/commands/dotnet-test/TestingPlatformCommand.cs	Updates invocation and parameter passing to support the new validation and BuildOptions usage.
src/Cli/dotnet/commands/dotnet-test/MSBuildHandler.cs	Removes redundant BuildOptions parameters and uses the class-level BuildOptions consistently.
src/Cli/dotnet/commands/dotnet-test/TestModulesFilterHandler.cs	Adjusts constructor and TestApplication instantiation to align with BuildOptions changes.

Comments suppressed due to low confidence (2)

src/Cli/dotnet/commands/dotnet-test/TestApplication.cs:92

• The updated condition now includes a check for !isDll, which may bypass using 'dotnet run' unexpectedly when running non-dll tests. Please verify that this logic change aligns with the intended behavior.

if (testOptions.HasFilterMode || !isDll || !IsArchitectureSpecified(testOptions))

src/Cli/dotnet/commands/dotnet-test/MSBuildHandler.cs:137

• Ensure that using the class-level _buildOptions in GetProjectsProperties is safe and that _buildOptions is always properly initialized to avoid potential null reference or state inconsistency issues.

(IEnumerable<TestModule> projects, bool restored) = GetProjectsProperties(solutionOrProjectFilePath, isSolution);