Only running search after input is finished

[PKFire813]

What did you fix?

Hard-coded a .5s (configurable) buffer in between the last change to the search and the final load, so that we weren't regenerating the search every single time.

"One is that some people were requesting searches in the various windows to only take effect when you press enter or similar, since the constant updates cause a fair bit of lag. "

Reproduction steps

---

Evidence/screenshot/link to line

https://gyazo.com/804e83bc2e6b2378afd819d5b89a46ab for gif of usage

Considerations

• Does this contain a new dependency? [No, but we are using a new library.] In order to smoothly include for the situations in which multiple letters are being changed within the .5 second SLA, we are using a different timing class. Instead of using Windows.Threading.Timer, we are using Windows.Systems.Forms (https://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.timer?view=windowsdesktop-7.0) instead. This class is easier and cleaner to have the timer be interrupted without spawning multiple unnecessary threads.
• https://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.timer?view=windowsdesktop-7.0
• Does this introduce opinionated data formatting or manual data entry? [No]
• Does this pr include updated data files in a separate commit that can be reverted for a clean code-only pr? [No]
• Have I run the linter? [No]
• Is is a bug fix, feature request, or enhancement? [Bug Fix/Enhancement]

[PeterJeff]

I'll run this in my builds for a while just to be but so far it seems sensible and works.

I'm just some interested rando though.

[dimon222]

LGTM