* ported tests from https://github.com/dotnet/roslyn/pull/21263

* added ref readonly test

* added more tests following PR suggestion

Fixes #22265

Fixes #22007

Address feedback and represent VB GetType as ITypeOfExpression and also revert unintentional change to solution file

addresses more PR feedbacks

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.

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).

Address feedback from the design meeting and only expose the top level ITranslatedQueryExpression IOperation for v1.

We longer expose any special IOperation nodes for query clauses/operators, but just the underlying query plan. For v2, we hope to enhance the APIs to expose a richer query API.

Another design decision was to rewrite VB query lambdas into regular lambda, so we have parity between C# and VB operation trees.
This change refactors the VB query lambda local rewriting code to be consumed from the VB operation factory for the same.
The rewriter introduces a large number of DAGs, and we handle them in the operation factory rewriter by cloning the duplicate bound nodes in the lowered tree.

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.

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.