Remote private Cpp tools in favor of using production tools available ambient...

Remote private Cpp tools in favor of using production tools available ambient in the build machines; VS 16.4 RTM should have the right tools that release/3.1 requires (#2282)

eng/Versions.props

@@ -64,8 +64,8 @@
     <!-- 
         Also in global.json 
         Used in Wpf.Cpp.PrivateTools.props/targets 
-    -->
     <MsvcurtC1xxVersion>0.0.0.9</MsvcurtC1xxVersion>
+    -->
     <!--
     This is the version of the test infrastructure package is compiled against. This should be
     removed as part of https://github.com/dotnet/wpf/issues/816 

eng/WpfArcadeSdk/tools/Wpf.Cpp.props

@@ -89,7 +89,7 @@
   </PropertyGroup>
 
   <PropertyGroup>
-    <UsePrivateCppTools Condition="'$(UsePrivateCppTools)' == ''">true</UsePrivateCppTools>
+    <UsePrivateCppTools Condition="'$(UsePrivateCppTools)' == ''">false</UsePrivateCppTools>
   </PropertyGroup>
   <Import Project="Wpf.Cpp.PrivateTools.props" Condition="Exists('Wpf.Cpp.PrivateTools.props') And '$(UsePrivateCppTools)'=='true'"/>
   

global.json

@@ -18,7 +18,6 @@
   "native-tools": {
     "strawberry-perl": "5.28.1.1-1",
     "net-framework-48-ref-assemblies": "0.0.0.1",
-    "dotnet-api-docs_netcoreapp3.0": "0.0.0.2",
-    "msvcurt-c1xx": "0.0.0.9"
+    "dotnet-api-docs_netcoreapp3.0": "0.0.0.2"
   }
 }