Pass through features, publicsign, and deterministic flags to the IDE

Fix DiaSymReader nuget version string calculation

Add support for paths with spaces in cibuild

Replacing unreachable exception with no-op in OperationVisitor

Address performance issues in the AnalyzerManager reported at…

Stop deploying extension in BuildAndTest.proj

Ignore accessors in SetMetadataName

Change how we format on certain commit chars from completion. Fixes #7768, #8228

Fixes #8498

2ed22626 caused CIBuild's to start deploying extensions
because properties are not inherited by nested MSBuild
instances. Actually pass down DeployExtension=false.

Address performance issues in the AnalyzerManager reported at https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/2078#issuecomment-181150995:

1. Replace use of ConcurrentDictionaries with Dictionary + lock.
2. Avoid unncessary ToImmutableArray invocations.

I also fixed up a subtle race condition in CompilationAnalysisValueProvider.TryGetValue for my last PR (see https://github.com/dotnet/roslyn/pull/8375/files#r52127390).

Temporarily skip one more PDB test

Now that I have changed the flow for formatting here, the formatter
could return no changes. In those cases, don't update the document.

Change version of Microsoft.DiaSymReader to 1.0.7 (release)

Update to the latest copy of SRM signature reader

Read Portable PDB directly in EEs instead of thru ISymUnmanagedReader

Update README for determinism job

Enable determinism job in Jenkins

..chars from completion. We used to call the formatting service from the
completion list with the span equal to that of the text that we
inserted, in all cases. This may not be the right approach in all cases
and that is manifested when we are formatting for a typed char that
happens to be the trigger character for the formatter as well. In such
cases we must find the right span to give to the formatter, or in other
words, the span the formatter would have come up with if it were
triggered first for the typed char. We do this by simply invoking the
appropriate formatting service API and giving it the typed char and its
position, which lets the formatting service to compute the appropriate
span.
We do this only when the completion's commit char is also
a trigger for formatting. In other cases, we continue taking the
existing code path of formatting by giving it a known span.

Fixes #7768, #8228

Deterministic Builds

Remove unused constants from VisualBasicCompilationOptions

Update config to match new versions of DSL/ghprb

Fix EnC issue with out of sync DocumentId