Check status throttle prevents jobs from being queued

In this commit, throttling on adding the check_status jobs was introduced: https://cgit.drupalcode.org/tmgmt_extension_suit/commit/?id=4702141e96b8...

The code that checks whether check_status jobs should be added is this:

/**
 * Returns TRUE if it's time to add items to check status queue.
 */
function tmgmt_extension_suit_is_add_to_check_status_cron_run_needed() {
  $interval = Drupal::config('tmgmt_extension_suit.settings')->get('interval');
  $cron_next = \Drupal::state()->get('system.cron_last', 0) + $interval;

  return ((int) \Drupal::time()->getRequestTime() > (int) $cron_next);
}

I believe the logic of this either provides no throttling, or prevents check_status jobs from ever being added, depending on the value of tmgmt_extension_suit.settings.interval.

system.cron_last is updated on every cron run. In order for check_status jobs to be added, the current request time needs to be interval seconds later than system.cron_last + interval.

If the interval at which cron is run is less than tmgmt_extension_suit.settings.interval, then system.cron_last + interval will always advance before the current request time. If the interval at which cron is run is greater than tmgmt_extension_suit.settings.interval, then check_status jobs will be added with every cron run.

I believe that in order for this throttle to be effective, TES would need to keep track of the last time check_status jobs were added, and check against that, rather than checking against system.cron_last