The SignTool now supports batch signing NuPkg in the same manner as
VSIX. Simplifying our infrastructure now to build everything and then
sign as a final step.

This commit just moves the sign phase after packing. The next set of
commits will merge more of the Microbuild logic into build.ps1.

Fix the comparer for sorting enums in SymbolDisplay by using the
Framework comparer for long.

Fixes #22507

Add missing -cibuild switch

Keep attribute on the same line as a member if they started on a single line

Fixed 'Add null check' refactoring

Fixed unexpected line break on InlineTemporary refactoring on anonymous type with comment

Include 'term' and 'description' xml items when under an 'item' tag.

# Conflicts:
#	src/Features/CSharp/Portable/InitializeParameter/CSharpAddParameterCheckCodeRefactoringProvider.cs
#	src/Features/Core/Portable/InitializeParameter/AbstractAddParameterCheckCodeRefactoringProvider.cs

Update Pdb2Pdb to 1.1.0-beta1-62225-01

The core work here is that we were pulling reference assemblies out of a folder with the name RoslynTools.ReferenceAssemblies. A while ago NuGet switched to unpacking all folders with lowercase paths. On Windows this continues to work fine as the filesystem APIs are case-insensitive, but this fails on Linux. By matching casing we can build both net461 and netcoreapp targets on any operating system. The inability to do this was the primary reason for CrossPlatform.sln, so there's now no reason for the solution and we can switch to using Compilers.sln, which is a more reasonable superset of everything in CrossPlatform.sln.

Fixes #20932

Build with Portable PDBs

Merge master to post-dev15.5-contrib

Merge remote-tracking branch 'upstream/master' into merges/master-to-post-dev15.5-contrib-20171030-065938

Port changes from features/remotels to post-dev15.5.-contrib

(required for TypeScript in the remote LS scenario)

* made NFW to bucket things better

NFW API allows caller to supply extra info to make bucketting better.

this takes advantage of that ability for certain exception types which we know inner or remote exception is more important than the generic outter exception.

* added more comments

Remove IConversionExpression.IsExplicitInCode

* dotnet/master: (21 commits)
  added completion set and fix all telemetry to track performance (#22811)
  porting named pipe fix from service hub. (#22863)
  remove duplicated reference in the test (#22787)
  Fix unit test failures from merge resolution
  fixed regression on using nuget (#22809)
  Fix few more doc comments
  When creating child items in Call Hierarchy, use the correct project
  Make tests easier to diagnose if the fail
  Remove duplicate test helpers and put overloads right next to each other
  Remove duplicate project references.
  Fixed some doc comments
  Address review feedback and remove IsExpression and IsStatement properties.
  Address more feedback from design meeting and expose IOperation.IsExpression and IOperation.IsStatement properties
  Namespace change for IOperation APIs
  Fix unit test
  Unit test changes for IOperation API changes
  Update the summaries and descriptions of these packages to not be wrong
  Remove exact version requirements in our Razor NuGet packages
  Test framework changes for IOperation API changes
  Fix IDE analyzers for IOperation API changes
  ...

Remove exact version requirements in our Razor NuGet packages

Remove duplicate project references.

Use Server GC on CoreClr

* log more info on reanalyze, and prevent re-analyze to create big hash set.

* removed unnecessary log and fixed test failure

* added reanalyze scope

* PR feedbacks.

* added time tracking to completion set.

from the point we start completion set to first time we are called from VS for best match (which indicate that completion set is actually shown to users first time for this particular completion session)

the event is vs/ide/vbcs/intellisense/completion

if completion is done without showing UI to users (etc or tab), then event will be marked as cancelled.

* added perf tracking to LB fix all.

there were already existing events so I just made those to include perf info (duration) as well.

among all those events, these 2 are ones we were planning to add

vs/ide/vbcs/codefixes/fixalloccurrencescomputation
this shows time from the point user invoked fix all to where we shows preview window to users.

vs/ide/vbcs/codefixes/applychanges
this shows time from user clicked Apply from preview window to where we actually applied the changes to VS

there are more events between them in case we want to dig in details later such as how long it took to calculate diagnostics, how many files are affected and etc.

also all related events have correlation id to group related code fix events. also for fix all case, it contains scope to show whether fix all is for document, project, solution.

* PR feedback. removed unnecessary parameter

* removed repeated correction id set

* updated comments.