Implement module to limit requests counting towards rate limit #19
Description
When starting up with several channels to monitor, a lot of yta instances can spawn at once (many of which will be discarded based on yta output) which can quickly exceed rate limit. By creating a module that governs all requests that count towards rate limit, the actions can be spaced out and dispatched from a queue one after another. I'm not sure if a safe rate is known (in which case, force that) but I envision a user setting to define how many seconds of wait should be between requests, to space them out equally.