Move find-refs from object browser over to the new streaming-far-window.

Add tests for simplifying type names

Based on discussions with SDK team, attempting to switch to using
`$(OutputPath)` for controlling our output directory instead of
`$(OutDir)`.  This is how the SDK recommends teams do it and need
to validate whether this will work for us or not.

Disabled more flakey tests which fail on a trivial PR.

Acquire the user's selection up-front if we're on the UI thread for lightbulbs.

Move helper API up as it will be using functionality in EditorFeatures as i refactor more of FAR.

Don't crash in NavigateTo with methods that have __arglist parameters.

Simplify how we go from a text-snapshot to a document in lightbulbs.

Allow properties to be passed with DefinitionItems for FAR.

Track down flakeyness in MoveType tests.

After investigating with jason, we've concluded this strange code was written
back in the days where roslyn workspaces and VS documents were not something
you could trust to be in sync.  So we had to have a lot of painful code to try
to detect and bail out when that happened.  This is definitely not necessary
now, and we can just use the simple and correct function we already hve for this
task.

Remove the synchrounous FindRefs codepaths for C# and VB.

Move the implementation of RQNames down to hte Feature-layer.

There are circumstances where the editor will call into us on hte UI thread and will then
block for results.  Right now this can deadlock as we may have kicked off work to the BG
that then awaits getting the selection back from the UI thread.  To avoid that, if we're on
the UI thread when we start, just go and get the selection and pass it along.

This wasn't previously flagged because this only comes into play if there is an error.  As
written the code will display "$echo isn't a variable" instaed of the actual error.

Fix issue with definite-assignment checking in 'inline-decl' with 'var-typed' locals.