[Tracker] Workaround MSBuild bugs

[natemcmaster]

Similar to this issue: aspnet/Mvc#5482, except that here I'm tracking the list of bugs we have worked around to implement VS 2017 support.

Check off when the workaround has been removed.

Resolution unknown

• dotnet pack - ProjectReference loses version information NuGet/Home#3953 - dotnet pack - ProjectReference loses version information
• Generate AssemblyMetadataAttribute when serviceable is true dotnet/sdk#490 - Generate AssemblyMetadataAttribute when serviceable is true won't fix. We resolved in our targets.
• allow dotnet pack to pack nuspec file without needing a csproj file NuGet/Home#4254 -Support xplat command line for packing nuspec

Should be resolved when upgrading to rc3

• dotnet pack should pack tools with the versions that the package was built against NuGet/Home#4063 - dotnet pack should pack tools with the versions that the package was built against. - Workaround removed in Upgrade to RC.3 BuildTools#149
• OutputType in test project templates microsoft/vstest#287 - OutputType=Exe required for .NET Core, but OutputType=Library required for .NET Framework test apps. Requires upgrade to Microsoft.NET.Test.Sdk 15.0.0-preview-20170106-0. orkaround removed in Upgrade to RC.3 BuildTools#149

Should be resolved when upgrading to RTM

• Specifying package path doesn't work with dotnet pack NuGet/Home#4321 Cannot pack .NET Core CLI tool
• Non-deterministic concurrency issues in solutions with multiple projects dotnet/sdk#475 - build in parallel breaks badly (our workaround is to build one csproj at a time)
• Solution target generation does not take into account imported targets dotnet/msbuild#1587 - Solution targets overriden by metaproj. (Workaround added in Workaround issue in solution targets in MSBuild RC3 Universe#472)
• runtimeconfig.json contains incorrect framework version dotnet/sdk#686 - runtimeconfig.json has incorrect version
• WorkingDirectory coming incorrectly for .NET Core and .NetFramework  microsoft/vstest#311 Tests run from wrong folder. Workaround added to Hosting, Razor, and others.
• [IMPORTANT] dotnet-test should return 1 if test execution fails for any tfm microsoft/vstest#283 - dotnet-test returns 0 on multi-tfm test projects

Relevant PRs to track:

• update nuget to 4.0.0-rc3 and sdk to 1.0.0-alpha-20170105-5 dotnet/cli#5214 - update CLI to NuGet RC3
• Updated version of Test Platform dotnet/cli#5234 - update CLI to latest VSTest
• Added OutputType to Microsoft.NET.Test.Sdk.target microsoft/vstest#310 - Fixes OutputType in test project templates microsoft/vstest#287
• fix package path issues when packing content into non-default locations inside nupkg NuGet/NuGet.Client#1135 - Fixes Specifying package path doesn't work with dotnet pack NuGet/Home#4321
• Ensure built-in and imported targets are respected by the solution pr… dotnet/msbuild#1590 fixes Solution target generation does not take into account imported targets dotnet/msbuild#1587

[natemcmaster]

We've removed workarounds.