[Change signature] Fix null reference crash in VB

Fix cross language generate constructor bugs

Do not introduce conditional conversions when they are not legal.

This makes sure correct position is used to determine enclosing binder for the node. Fixes #49997.

Use the same type character that the user already uses in their enum

Make change signature more async and remove UI dialogs from the service

The problem here was when we do cycle detection, we tried to look
at the source of the candidate constructor that we are looking at
delegating to. If we are in a cross-language case, the target might
be from metadata via the skeleton reference and we don't have source.
Rather than fixing the code that assumes it's a source method, I'm
making a change that says if the constructor you're delegating to is
in the base type, then we can't create a cycle and can skip the check
entirely.

We tried to locate a constructor to delegate to; in that case we would
grab the types of the constructor and make sure the original call site
actually can use those types. In the cross-language case, we'd mix up
types from different languages. The correct behavior here is to map
the candiate type back to the language of the call site, since it's
the call site's language rules that matter.

Fixes https://github.com/dotnet/roslyn/issues/49850

Set AsynchronousOperationListener audience in Service.props

* Correctly handle default and params arguments in cfg for pattern based disposal

Set EnforceOnBuild values for code style analyzers

Add a debug check to ensure all CodeStyle diagnostic descriptors have EnforceOnBuild custom tag + Fix the missing tag for IDE0043 identified from this assert

Signature Help: Prefer non-obsolete overloads 

* Async-ify a bunch of things

* Failing tests

* Use the field naming style when generating types

Add tooling to CodeStyle layer to generate global configs

Specify publishing location for Microsoft.CodeAnalysis.Collections

 Show generated files live in Solution Explorer

Signed builds are failing because they don't know where to publish this package - https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=4308605&view=logs&j=20fcf628-b65c-5865-625a-1cef81cda63b&t=7efdce5b-215a-5afd-980e-58e9cb1ef7e6&l=26

Per @sharwell since this is similar to MS.CA.PooledObjects / MS.CA.Debugging we'll use the same arcade feeds