consider using throttle instead of debounce on requests

Nobody has claimed this yet.

We use debounce to slow down requests to the Geocoding API, however I've noticed that when typing a search input, I'll often keep typing more of the query since I still haven't seen any suggestions, where I'd actually prefer some suggestions to start showing up while typing.

If we used throttle instead of dobounce, then some suggestions could start to show up even while still typing, and the user could then decide oh hey there's the suggestion I want, I'll stop typing and select it.

Would be preferable to decide which way to go here before #185

Start by locating the current debounce-based Geocoding API request path and review issue #185 before evaluating the scheduling options. Done means the request behavior and expected suggestion timing are agreed and verified; the issue does not name a file or test.

Written by the indexing model from the issue text.