[vcpkg] Download vcpkg.exe rather than building it in bootstrap on Wi…

…ndows. (microsoft#15474)

This reduces bootstrap cost for Windows customers, resolving the issue initially submitted as microsoft#12502 .

The `toolsrc` tree was extracted to https://github.com/microsoft/vcpkg-tool. `bootstrap.sh` was changed to download the right source tarball, extract, and build it. This was chosen over the previous attempt, a submodule, over concerns of accidentally destroying people's local modifications.

.gitignore

@@ -11,8 +11,6 @@
 *.userosscache
 *.sln.docstates
 
-toolsrc/out*
-toolsrc/CMakeSettings.json
 # fuzzing
 sync_dir*
 
@@ -30,8 +28,6 @@ bld/
 [Bb]in/
 [Oo]bj/
 [Ll]og/
-# VS Code build
-toolsrc/build
 # Ignore the executable
 /vcpkg
 /vcpkg.exe
@@ -290,11 +286,6 @@ __pycache__/
 /installed*/
 /packages/
 /scripts/buildsystems/tmp/
-/toolsrc/build.rel/
-/toolsrc/windows-bootstrap/msbuild.x86.debug/
-/toolsrc/windows-bootstrap/msbuild.x86.release/
-/toolsrc/windows-bootstrap/msbuild.x64.debug/
-/toolsrc/windows-bootstrap/msbuild.x64.release/
 #ignore custom triplets
 /triplets/*
 #add vcpkg-designed triplets back in

docs/about/privacy.md

@@ -41,7 +41,7 @@ We collect various telemetry events such as the command line used, the time of i
 
 You can see the telemetry events any command by appending `--printmetrics` after the vcpkg command line.
 
-In the source code (included in `toolsrc\`), you can search for calls to the functions `track_property()`, `track_feature()`, `track_metric()`, and `track_buildtime()`
+In the source code (included at https://github.com/microsoft/vcpkg-tool/ ), you can search for calls to the functions `track_property()`, `track_feature()`, `track_metric()`, and `track_buildtime()`
 to see every specific data point we collect.
 
 ## Avoid inadvertent disclosure information