We should update the InvokeTestingPlatform target so that it produces an error when VSTest-specific command-line switches are used. We will add a property to opt-out from the error.

These properties should be:

• VSTestSetting
• VSTestListTests
• VSTestTestCaseFilter
• VSTestTestAdapterPath
• VSTestLogger
• VSTestDiag
• VSTestResultsDirectory
• VSTestCollect
• VSTestBlame
• VSTestBlameCrash
• VSTestBlameHang

1. This is a breaking change, but I believe it's for the good. We have seen many users confused in the past because they do dotnet test --filter something and wondering why the filter is ignored. Or dotnet test --logger trx, etc..
2. It's not ideal that MTP will be aware of these VSTest-specific properties, but I think it's minor in this case.

This approach allows us to still keep dotnet test (without any argument) to work in mixed mode.

FYI: @OsirisTerje @rprouse @thomhurst @bradwilson