Refactored BoundLocalDeclaration to have separate initializers for Array bounds and the standard declaration.

* dotnet/master:
  Address a number of IOperation issues for VB (#22795)
  Ensire that IOperation nodes representing param arrays and default values are properly marked as implicit. (#22758)
  Verify symbol
  Update AssertEx.SetEquals to print better output
  Add a test to ensure search after an edit actually works
  Allow null MethodGroup.Receiver in error cases
  Report non-fatal exception telemetry if we have an issue
  Guard against the project being removed
  Don't have AbstractCallFinders hold onto projects
  Don't use Assert.True if we have a better assertion
  Ensure we always complete the call hierarchy search
  Avoid leaking documents if an exception is thrown in AddDocument
  Convert unreachable code analyzer to a semantic model analyzer

Avoid leaking documents if an exception is thrown in AddDocument

Convert unreachable code analyzer to a semantic model analyzer

Allow null MethodGroup.Receiver in error cases

1. Ensure correct syntax nodes and implicit state are used for IArgument nodes matching OmittedArgumentSyntax. Fixes #22486.
2. Ensure correct argument kind is associated with synthesized arguments within query expressions. Fixes #22066.
3. Ensure the invariant that “each syntax node has at most one corresponding explicit IOperation node” is met for all test scenarios we have at the moment. In order to achieve this the following changes are made:
-mark some synthesized bound nodes as compiler generated.
-for assignment statements, ensure that ISimpleAssignmentExpression and ICompoundAssignmentExpression nodes are marked as Implicit because they are sharing syntax node with containing IExpressionStatement and VB doesn’t have a concept of an assignment expression.
-for throw statements, ensure that IThrowExpression node is marked as Implicit because it is sharing syntax node with containing IExpressionStatement and VB doesn’t have a concept of a throw expression.
-for Add/RemoveHandler statements, ensure that IEventAssignmentExpression node is marked as Implicit because it is sharing syntax node with containing IExpressionStatement and VB doesn’t have a concept of an event assignment expression.
-ensure that receivers for IPropertyReferenceExpression representing references to query range variables are marked as implicit.
-ensure that IPropertyReferenceExpression and IParameterReferenceExpression nodes representing references to query range variables are associated with correct syntax nodes.
-ensure that return statements and blocks in query lambdas are marked as implicit.
-for IInterpolatedStringText node, ensure the underlying ILiteralExpression is marked as implicit because it is sharing syntax node with its parent.

Ensire that IOperation nodes representing param arrays and default values are properly marked as implicit. (#22758)

Fixes #21451.

Fix several issues with Call Hierarchy

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems?id=481125

* Update PDB converter to 1.1.0-beta1-62221-01

* Enable more conversion tests

The use of Assert.True() is confusing as you end up with:

Expected: [set]
Actual: [another set]
Expected: True
Actual: False

This dispenses of the second expected/actual.

Before this, if we couldn't find the project we'd throw exceptions
and possibly crash or do something bad.

Holding onto Project directly meant the snapshot would be leaked. We
should only hold onto the SymbolKey so we can resolve it later.

* Closes #18171

* ReadOnly Tuple Structs

* Closes #18172

If a symbol couldn't be resolved, we would bail the search and never
notify the UI that we stopped searching. We also wouldn't complete
the IAsyncToken either.

While I was here I also noticed that we were starting the async
operation asynchronously which could have resulted in flakiness in
integration tests. Our pattern is anything starting async work should
start the operation right away, so we can confidently wait until the
operation is complete.

# Conflicts:
#	src/EditorFeatures/Core/Implementation/CallHierarchy/Finders/AbstractCallFinder.cs

* made children not to return null and reorder children in evaluation order

* added some verification

* fixed formatting

* fixed ordering

* removed temp variable.

Make invalid call IInvalidExpression

Add CodeStyle packages to the PreReleaseOnlyPackages list

Fixes #22679. Fixes #7397. Related to #22029.

Do not expose implicit IInstanceReferenceExpression in an IDelegateCreationExpression targeting static method. (#22706)

Fixes #15513.