Completion items can no longer provide custom spans.  Instead, it is always provided by the completion list.

This adds back `src/Compilers/Core/Portable/Interop/IVsSQM.cs` file and re-adds it to the `src/VisualStudio/Core/Def/ServicesVisualStudio.csproj` project because there is a some VS code with IVT that currently depends on the interop type existing.

These tags were missing from the telemetry vsix and the setup.next vsix.

The visitor automatically visits a node's parent if the node doesn't produce a string.
Visit the Name of a MemberAccessExpression in a way that won't visit the parent.

Combine Kernel32.cs, Ole32.cs and User32.cs into a single NativeMethods.cs. The distinction is not meaningful

* Add ClearEditor() API to editor tests that is called at the start of each test
* Add named parameters to VerifyCurrentLineText(...) and VerifyTextContains(...) test helpers to make it clearer when the caret position is specified and intended to be asserted
* Move calls which wait for async operations into the APIs and out of test helpers
* Other minor tweaks

This change makes SendKeys less flaky and removes the delay between characters, which was hiding bugs. Now, we just wait for application idle before blasting keys to the VS process. Additionally, I've started more cleanly separate code that runs in process vs. out of process.

This makes it more natural to set up tests where the editor is expected to have some code and the caret is expected to be positioned. This also removes some crusty DTE code that was executed over RPC.

This is the initial punch through that contains:

- A few more tests ported from CSharpAutomaticBraceCompleteion
- Tons of clean up (and more to come) in the SendKeys implementation
- Fix for incorrectly defined `VkKeyScan` Win32 API P/Invoke (needs to be unicode CharSet!)
- Fix code which tests text before and after caret
- Fix loads of bugs in the existing tests