This is 3-fold, this should:
- ease the listener's work to only deal with required tasks (the ones that are still
scheduled through the initial scheduler-runner, e.g. save code now, deposit, vault,
...). The other tasks scheduled with the next-gen scheduler no longer needs to report
such status as a dedicated journal client is in charge of that part. -
- also decrease the load induced by those update in the scheduler db
- help the save code now have better status report (it's still using the scheduler db to
access some of those status as fallback).
This is the other side of the configuration adaptation done in the swh.scheduler.task
module [1]
Related to T3458
[1] Related to D6405