Pause a short while before computing if fixes or refactorings are available at a particular line

[CyrusNajmabadi]

This drops the CPU usage used while scrolling by 12%:

down to:

--

The call we are getting here is made from the editor to determine if they should show the lightbulb at all. While scrolling, we get this call every time the line changes. So we kick off the work instantly, then cancel it, then kick it off, then cancel it, over and over again.

This changes us to just not bother until a very short time has passed (100ms). This is slow enough that we don't even bother for almost all times. But fast enough that it's not noticeable, and actually moving to a line will show the lightbulb very quickly if you stop on it.

[CyrusNajmabadi]

Waiting on @kayle to ensure that this won't be a telemetry concern.

Kayle this is not the action of the user bringing UP the lightbulb. Rather, this is the code that runs when the editor determines if a lightbulb should be shown on a light, and what sort of lightbulb to show. will this have any issues with telemetry? like will thsi show as some massive regressions somewhere?

[CyrusNajmabadi]

@ToddGrun ptal

[ToddGrun]