[release/10.0.1xx] Fix solution parsing in dotnet test for Microsoft.Testing.Platform

[Youssef1313]

This backports #51411

Description

This PR backports #51411. It's a fix for dotnet test for Microsoft.Testing.Platform (a new feature in .NET 10) where we didn't parse solution files correctly. This resulted in two categories of issues:

1. All projects in solution were considered build-able and we attempted to evaluate them. But shared projects are (one) example of a project that shouldn't be build-able.
2. Not passing the correct values of Configuration and Platform global properties. Normally, when building a solution, projects are passed Configuration and Platform global properties. The lack of passing these global properties can result in wrong evaluation in the project, for example, ending up looking for the test executable in the wrong directory, and failing because it's not found.

Customer Impact

This was reported both internally and externally. Related issues:

• [dotnet test][MTP]: Failing to run solution filter that contains shproj #51398
• dotnet test should respect platform #51481
• Project file falsy considererd as VSTest project instead of MSTest project microsoft/testfx#6948
• Update to .NET 10 SDK and MTP CommunityToolkit/dotnet#1141 (comment)

Regression?

Technically no, it's a new feature. But if a user is migrating from VSTest to Microsoft.Testing.Platform, they might view it as a regression.

Risk

Low.