Merge master into future

Conflicts:
	src/Debugging/Roslyn.Reflection.Metadata.Decoding/SignatureDecoder.cs
	src/Features/CSharp/Portable/CSharpFeaturesResources.resx

Merge tuples to future

Move Signature Help to features layer

Most of this PR is invisible.

What I did was pull down the current toolset packages from azure and replaced the files in the dotnet-cli folder with new ones downloaded from https://github.com/dotnet/cli

Merge master into future

- Added support for properties and events in tuple type symbol.
- Made additional adjustments to implementation of tuple symbol display around presence of element names.

Conflicts:
	Makefile
	src/VisualStudio/CSharp/Impl/CSharpVSResources.resx
	src/VisualStudio/CSharp/Impl/Options/AutomationObject.cs
	src/VisualStudio/Core/Test/ServicesVisualStudioTest.vbproj
	src/VisualStudio/VisualBasic/Impl/BasicVSResources.resx
	src/Workspaces/Core/Portable/Workspaces.csproj

Use nameof() instead of string literals in ArgumentExceptions

Fix NRE and provide better verbosity

Update the diagnostics rolling perf tests

Use threadlocal storage for pooling our matrices.

1. Split out the tests into ones with built-in IDE analyzers and ones with only third party analyzers
2. Tests depends on closed side changes (add/update VS tao actions)

Merge master into future

Add options to enable/disable nuget search.

Conflicts:
	src/Compilers/Core/Portable/PublicAPI.Unshipped.txt
	src/Dependencies/VisualStudio/project.json
	src/Features/CSharp/Portable/CSharpFeatures.csproj
	src/Features/Core/Portable/Features.csproj
	src/Workspaces/Core/Portable/PublicAPI.Unshipped.txt

Make completion service public

Fix automation to fetch

Remove ProjectSystem code

Reenable CurrentWorkingDirectory_Change

There are 2 changes here
1. Move some of the helpers from test_util to tools_util since the helpers are not depended on the helper binary and can work without any dependencies
2. Introduce TriggerAutomation.bat, which triggers the automation process.

The reason we need a bat file to trigger this and not a csx or a new csx is because running the csx requires the helper binary. Hence we need to run the csx files from the binaries folder but we cannot have binaries in place if we dont fetch them in the first place. This is a cyclic problem that has to be broken with the help of one initial Trigger Batch file

- Substitute underlying type with corresponding tuple type at the point of type reference.
- Adjusted implementation of symbol display to account for presence of names in the extension tuples.
- Implemented proper retargeting for tuple types (multi-targeting support).

This code has been moved to http://dotnet/roslyn-project-system

Temporarily disable test CurrentWorkingDirectory_Change