Enable logging of informational telemetry for analyzers/fixers/refactorings executed during Ctrl + .

If user enables informational RoslynEventSource telemetry following the steps at https://aka.ms/reportPerf, we log the execution times for each analyzer/fixer/refactorings when computing the code fixes and refactorings to show in the light bulb. This will help us identify slow analyzers/fixers/refactorings that lead to UI delays with "Gathering suggestions" dialog.

* Remove BaseSolution property

* Refactor GetAllAddedSymbolsAsync

* Track documents that do not match the debuggee

* Handle design-time-only documents and documents with no sequence points

* completion leaking cancellation exception

* code review feedback

* feedback addressed

* fixing more merge conflicts

* Update CommitManager.cs

Now that the old code is dead, we don't need to qualify things anymore.

My previous commit deleted this interface and a constructor that
consumes it. But TypeScript is still MEF importing the interface just
to pass it to the constructor; this adds both of those back. Once
TypeScript is off of this constructor this commit can be reverted
verbatim.

Now that the editor has their own public version of this API, and all
code has been migrated to use the new system, we can delete all of the
code that was supporting the old handlers. It may be surprising that
much of this code was dead, but the command handler list that was being
invoked by all of this was indeed empty.

The intent of this particular commit is to be a fairly mechanical change
that leaves other bugs or strangeness in place. In particular,
DebuggerIntelliSenseFilter had a special ExecuteVisualStudio2000 that
removes the buffer's read-only flag, but in many codepaths we never
set that back. In other cases, we also ignored the HRESULT that came
from the next filter in the chain. These all appear to be bugs, but I
won't touch them for now.

There's also some remaining work happening in
AbstractOleCommandTarget.Execute.cs that probably should either be moved
to the core editor code (if it wasn't already), or into the command
handlers of Roslyn itself.

Now that TypeScript has moved to the newer editor commanding APIs,
the legacy implementation is no longer needed.

reverting back to LIst. turns out I dont need it to be enumerable since I changed code to use GetOrCreateClassifedSpanList

Fix unit tests

tweaked a bit more so that we dont run anything on UI thread for syntactic classification

add latency tracker to the new tagger