Add ControlFlowGraph.Create overload that takes syntax and semantic m…

Infrastructure misc changes

Create Control Flow Graph regions to designate life-time of flow captures in a Control Flow Graph. A region should start as soon as a capture is needed to accurately represent the order of evaluation within operations involving control of flow. However, it should not start too soon. For example, if there is a branch that represents an execution path that bypasses the use of a capture completely, that branch should not be included into the region for the capture. Also, the region should end as soon as the last operation referencing the capture is reached.

Added 15.8-preview3 builds to README

* Use System.Runtime.Loader light-up package

Expose IOperation.SemanticModel

bug fix: don't optimize interpolations when in an expression lambda

Remove testoperationvisitor workaround now that bug is fixed.

Skip 3 failing NetCoreTests until fixed

Unskip test for fixed IOperation issue

Move to new MSBuild drop

Original issue: https://github.com/dotnet/roslyn/issues/23821

Correct doc about Equivalence Key

Test alias to forwarded type

Stop calling IVsHerarchy.ParseCanonicalName if we don't need it

* Only import package versions in projects that restore toolset packages

* Add nuget.org feed

Resolve function to native offset uint.MaxValue

Don't push an empty batch of projects

Previously the FunctionResolver used 0 for the native offset of all
instruction address of resolved function names. The debugger inteprets
this literally, which causes function BP's to be bound on the first
native instruciton of a JIT'd method. This is incorrect as the bp should
be bound to the native instruction that represents IL offset zero. The
function resolver should use uint.MaxValue for native offset to
communicate that the instruction address always represents IL offset 0,
even for a JIT'd method.

Fix bugs related to IAnonymousObjectCreationOperation

Avoid stealing focus from the active output window pane