See https://github.com/dotnet/roslyn/issues/21385#issue-248857857

I also found that Range and Relational case clause have no tests in VB. Additionally, I also marked all OperationAnalyzerTests with CompilerTrait attribute so they don't get skipped in local trait based testing.
Fixes #22129

1. Fix test issues
2. Remove IHasDynamicArgumentsExpression interface and move the Arguments property from it to individual IDynamicXXXExpression nodes.
3. Adjust the extension methods for GetArgumentName and GetArgumentRefKind accordingly.

Regex used:

rg 'new CultureInfo' --files-with-matches | xargs sed -Ei 's/new CultureInfo\("("?[^"]*"?)"(, false)?\)/new CultureInfo("\1", useUserOverride: false)/'
rg 'New CultureInfo' --files-with-matches | xargs sed -Ei 's/New CultureInfo\("("?[^"]*"?)"(, False)?\)/New CultureInfo("\1", useUserOverride:=False)/'

In preparation for a merge of features/ioperation to master, we have decided to internalize all the IOperation APIs which are either not tested or not reviewed by the design team.
This includes the following APIs with bugs tracking reviewing/adding tests for them: IArrayElementReferenceExpression(https://github.com/dotnet/roslyn/issues/22006), IAwaitExpression(https://github.com/dotnet/roslyn/issues/22007), ICatchClause(https://github.com/dotnet/roslyn/issues/22008), IEndStatement(https://github.com/dotnet/roslyn/issues/22004), IPlaceholderExpression(https://github.com/dotnet/roslyn/issues/21294), ISizeOfExpression(https://github.com/dotnet/roslyn/issues/21296), IStopStatement(https://github.com/dotnet/roslyn/issues/21297), ITryStatement(https://github.com/dotnet/roslyn/issues/22008), ITypeOfExpression(https://github.com/dotnet/roslyn/issues/22003), IWithStatement(https://github.com/dotnet/roslyn/issues/22005)

This change also includes a simple API rename: IMethodBindingExpression renamed to IMethodReferenceExpression(https://github.com/dotnet/roslyn/issues/21289).

* Use DSRN version 1.7.0-beta-25631

* Fill in missing document entries in PDB tests

* Update pdb to xml converter to 1.1.0-beta1-62106-02

1) Use IDynamicInvocationExpression for VB late bound invocation and C# dynamic invocation.
2) Use IDynamicIndexerAccessExpression for C# dynamic indexer access; not used in VB.
3) Remove IDynamicObjectCreationExpression.MemberName property.
4) Add extension methods on IHasDynamicArgumentExpression to get optional argument name and ref kind for an argument at a given index.

These projects reference the compiler EXE projects and hence copy them
to the output directory. This appears to not cause the correct
app.config file (ex csc.exe.config) to be copied along with it. It's
missing the necessary binding redirects that are generated from a direct
compile of the project. As a result when it' invoked from the unit tests
it fails.

It's possible this is a SDK bug and I will dig into that. For now though
I need to unblock the suites.

This changes the unix legs to use the 2.0 SDK. They are likely to suffer from the
same problem as the windows CoreClr leg in that they aren't producing XML files. But
we should be able to fix both of those at the same time.

This primarily moves us to the 2.2.0 version of xunit. In order to make
that transition though a number of other changes needed to happen as
well:

1. Needed to move our desktop target to 4.6.1. This should've been
required some time ago but we were essentially depending on bugs in the
SDK / NuGet.
1. Remove the DeployCoreClrTestRuntime project. This entire idea
depended on having the xunit.console.netcore package. This has since
been deleted and doesn't work with the 2.0 SDK.
1. Remove the deploy compiler tools project. Can just use dotnet exec
now and that's much more efficient.
1. Resolve a new ambiguity with KeyValuePair. A helper of ours now
exists in netcoreapp2.0.

I fully expect a number of Jenkins legs to fail with this change: build
correctness, coreclr and ubuntu. But I want to validate our other legs
and am still trackind down answers needed to fix the others.

1. Add Locals property to ILoopStatement
2. Remove IterationVariable from foreach loops and VB ForTo loops.
3. Add InvalidCondition to Do loops for VB error cases.
4. Rename property AddLoopBottomExpressionList to NextVariables
5. Add relevant unit tests
6. Remove ISyntheticLocalReferenceExpression and SyntheticLocalKind