Update all test sdk references to the latest version.

[marcpopMSFT]

I don't think we have a good way of doing the version listed in the versions.props in a test itself (rather than a test asset built ahead of time). Open to suggestions on how to solve that.

For the rest, I don't know if the test infrastructure for those tests includes the version.props which could limit how many of these I can update.

[marcpopMSFT]

@dotnet/dotnet-testing I was talking with @Evangelink and he noticed that we had a bunch of old microsoft.net.test.sdk references so I tried to update them all.

Microsoft.NET.ToolPack.Tests.GivenThatWeWantToTestPackAToolProject.Microsoft.NET.ToolPack.Tests.GivenThatWeWantToTestPackAToolProject.When_app_project_reference_a_library_it_flows_to_test_project is failing with an odd error now that I updated the test sdk version. Anything you've seen before? Any suggestions? I'm not sure why it's timing out.
Failed to negotiate protocol, waiting for response timed out after 90 seconds. This may occur due to machine slowness, please set environment variable VSTEST_CONNECTION_TIMEOUT to increase timeout.

[MiYanni]

Good idea. Almost sounds like we should have a Version.props file just for the tests? Like, I see the fixed xunit versions in here too. I think all the tests should have a central location for their test packages, unless the test is testing a specific version of a package.

[Evangelink]

Failed to negotiate protocol, waiting for response timed out after 90 seconds. This may occur due to machine slowness, please set environment variable VSTEST_CONNECTION_TIMEOUT to increase timeout.

This is a quite common issue with VSTest but it can have many sources. I'll try to read the logs next week.