Improve VS Code build current project support

Co-Authored-By: NRikki Gibson <rikkigibson@gmail.com>

Support a single OOP call to perform all of rename, on top of the individual pieces of rename that are already OOPed

🐇 Avoid computing unnecessary semantic models

This makes the following changes to our ability to build the current
project from VSCode (essentially implementing the rough equivalent of
build current project in VS).

- Ability to choose `msbuild` in addition to `dotnet msbuild`. The full
framework `msbuild` is still necessary for building parts of the IDE
code base.
- Support for VB projects
- Fixes the execution of the task on Windows. The hard dependency on
`/.dotnet` existing doesn't hold on Windows. Falling back to normal
powershell in that environment

Add overload for rpc that can work on streams, not just object writers.

Move the 'application/validation/resolution' portion of rename OOP.

🐇 Implement AsyncQueue<T>.TryDequeueAsync

Update SQLite interop following code review

Co-Authored-By: NAndrew Hall <ryzngard@live.com>

* Update System.Memory version

This should automatically update System.Numerics.Vectors, which is needed by the MSBuild team to add a new dependency on System.Text.Json, which is used in adding support for solution filter files in MSBuild.

* Update System.Buffers version

System.Memory depends on it being updated.

For tuple types, NamedTypeSymbol.GetFieldsToEmit API should return symbols for tuple underlying fields. (#43552)

Fixes #43524.
Related to #43549.

Also, ensure nested type is generated for a fixed size buffer declared within a tuple type.

Related to #43621.

Closes #24517

Fix flow of nopia build props