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.

Fixes
https://devdiv.visualstudio.com/DevDiv/_workitems?id=391561&_a=edit&triage=true

Provide an appropriate span for refactorings so we can better prioritize them against fixes of the same priority.

In order to gather more information on
https://devdiv.visualstudio.com/DevDiv/_workitems?id=209299, we created
https://github.com/dotnet/roslyn/pull/16918 to capture the text of the
linked documents that aren't in sync. However, we tried to do so by
putting their text in local variables that were optimized away in dumps.

This change introduces a custom exception object that holds onto the
text of the conflicting documents and reports that exception.

Only filter if this is a simple retrigger command.  We don't want to filter out a command that has data we might need.

also, now merged separate vs telemetry logger to one since telemetry activity is now obsolete. also remote host also now share logger since both is now on new API

moved remote host check inside of each ToDo and Designer Attribute service so caller doesn't need to care about it.