Remove @allouis' throttle

@remy's version was throttled 200ms *after* user interaction, whereas @allouis' version fires, then debounces for another 200ms. This is fine if the action is truly async, but it's not: there's an iframe being rendered as the user is typing. So if we do all the iframe work *as soon* as the user starts typing, it introduces latency. Compared to firing after 200ms if idle from the keyboard, the user has finished typing, and we have a moment where we can slip in and render the iframe, thus avoiding *some* latency.