Enforce more code style rules as build warnings in IDE projects

🐇 Avoid using an ArrayBuilder for IntervalTree<T>.Any

Enable completion assertion in AnalyzerDriver

Do not remove cast when it would break a params call.

🐇 Avoid making two copies of SyntaxToken at each step of the formatting operations chain

Use consistent namespaces for integration tests

Revert "Remove Razor IVTs"

Don't remove casts in conditional expressions if it would change the meaning.

Update inline rename code following completion of TypeScript external access work

Don't remove null-casts in switch expressions

Don't offer to use System.HashCode when the existing GetHashCode is already simple enough.

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.