Run VSTest tests with MTP

[Youssef1313]

TODO:

• Move to .NET 10 and Arcade 10 (@nohwnd is that part okay for you? - I assume moving to MTP generally is good, unless you see any technical blockers but there probably none?) - I'll follow-up in a separate PR.
• Add dotnet.config
• Set OutputType to Exe in test projects

[nohwnd]

moving to net10 should be okay. Moving to mtp should also be okay. We are using an already released version to run the tests anyway, so we are not losing "coverage" by moving to another test runner.

[nohwnd]

nit: move this below the -nobl or the otherway around

[Youssef1313]

failed RunAllTestsWithMixedTFMsWillProvideAdditionalInformationToTheDebugger (Row: 19, Every runner, Runner = net8.0, TargetFramework = net8.0, InIsolation,  vstest.console = 17.6.2 [MostDownloaded],  Testhost = 17.15.0-ci [Latest],  MSTest = 3.9.3 [LatestStable]) (16s 791ms)
  Expected collection to be empty, but found at least one item {"The active Tests Run was aborted."}.
    at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
    at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason)
    at FluentAssertions.Execution.GivenSelector`1.FailWith(String message, Object[] args)
    at FluentAssertions.Execution.AssertionChain.WithExpectation(String message, Action`1 chain, Object[] args)
    at FluentAssertions.Collections.GenericCollectionAssertions`3.BeEmpty(String because, Object[] becauseArgs)
    at Microsoft.TestPlatform.AcceptanceTests.TranslationLayerTests.CustomTestHostTests.RunAllTestsWithMixedTFMsWillProvideAdditionalInformationToTheDebugger(RunnerInfo runnerInfo) in /_/test/Microsoft.TestPlatform.Acceptance.IntegrationTests/TranslationLayerTests/CustomTestHostTests.cs:158
    
  Standard output
    Available space for TEMP: D:\ 85151 MB
    Logging diagnostics in D:\a\_work\_temp\vstest\kTfAa\log.txt
    Console runner path: D:\a\_work\1\s\.packages\microsoft.testplatform.cli\17.6.2\contentFiles\any\netcoreapp3.1\vstest.console.dll

😕

[nohwnd]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).