This causes problems if we're spinning up a workspace on a background
thread. Let's defer until actually having to fetch metadata, which we
don't do in most cases anyways.

It's still obsolete, but adding it breaks people trying to compile
with warn as error enabled.

Fixes #14202

Some more automated tests and test cleanup for the PR#16659

* add end to end stack depth test

* add comment explaining test

* switch to verify diagnostics

* turn parallel build off

* check pointer size in addition to debug/release

removed additional cost I can find from trace compared to code before…

Enable Code Fixes in F# (RC3 regression)

https://github.com/dotnet/roslyn/pull/16659

added tests, made the included tuple2 chunk a CData

Fixes #16352

We're on the UI thread, do the proper step to initialize.

The contract is to return null if the ProjectId didn't come from us.
If we don't have deferred state, then we're not even initialized so
it most definitely didn't come from us.

Fixes Microsoft/visualfsharp#2329

In 44142e5f I removed this code, under the belief that it wasn't
a problem. However, when WpfFact-attributed tests run, we clear the
foreground thread. Some static state (namely the
ForegroundNotificationService) is still trying to operate between test
runs, so it'd see the fallback state and then bad things would happen.
Although there's a number of terrifying things there, for now we'll
just roll it back.

Implements GetDeclaredSymbol for tuple literals and GetSymbolInfo for elements of tuple literals.

Merge dev15-rc3 into master

Enable override completion to use expression body accessors

Disallow Rename Tracking on named tuple elements (to match Inline Rename and prevent a crash)

The subsumption tree must treat an unconstrained type parameter as possibly null.
Also, if a previous case pattern handles all non-null input, any further case type pattern is subsumed.
Fixes #16688
Fixes #16671

Fixes #16559

Fixes #10765

They were building as 64-bit only since there wasn't a 32-bit CoreCLR before.

Small builds changes for end to end source build

Couple of infrastructure updates

added unit test

Unfortunately CodeLens (and others) might still be doing this, so
we won't assert if it's already been initialized. This is risky but
restores to closer to the original behavior until we can get all
callers updated.

If we try deferring this, we might end up calling it on the first thread
to raise an event, instead of thread that created the workspace, which
was our previous contract. The default implementation looks at whether
there is a SynchronizationContext to determine what the scheduler is
to use, so the change matters.

The VsdConfig.targets file was not located in our core targets location.
Moving there as this is the appropriate place for all targets / props
files in our build.

Additionally changed it to use the vsdconfig from our NuGet packages
directory instead of hard coding Visual Studio.

Properly detect and handle delegate relaxations when ByRef returns are involved.

Disable some of our analyzers from running on generated code files.

Fixes #15971