Use dotnet run in case of --arch in dotnet test

[mariam-abdulla]

This pull request includes several changes to improve code readability and consistency in the dotnet-test command implementation. The most important changes involve making variables readonly where applicable, renaming variables for clarity, and refactoring methods to reduce redundancy.

Codebase Improvements:

• Made _output and _executionIds readonly in MSBuildHandler and TestApplication classes respectively to ensure immutability. [1] [2]
• Renamed variables from modules to projects to better reflect their purpose in the MSBuildHandler and MSBuildUtility classes. [1] [2] [3] [4] [5]
• Refactored RunAsync and related methods in TestApplication to use TestOptions instead of multiple parameters, simplifying method signatures and improving readability. [1] [2] [3] [4] [5]
• Updated BuildOptions and TestOptions records in Options.cs to include new fields and improve clarity.
• Modified GetProjectProperties in SolutionAndProjectUtility to accept globalProperties parameter, enhancing flexibility.

Relates to #45927

[Evangelink]

I don't see tests added for architecture with and without filter. Are the tests already existing?

[mariam-abdulla]

I don't see tests added for architecture with and without filter. Are the tests already existing?

Without filter, yes (we have RunTestProjectSolutionWithArchOption_ShouldReturnZeroAsExitCode)
With filter, we still need to discuss this part. So, I still haven't added tests for it.