As of today, the indexer tasks are scheduled through a volatile scheduler  to:
- avoid cluttering the (scheduling) database (softwareheritage-indexer) with message too long (T991)
- check multiple queues prior to scheduling new ones
The indexer stack has been developed prior to the scheduler.
Now the orchestrator part seems redundant and induces quite some complexity.
If this is replaced by the actual scheduling part, it seems the point 2. can be addressed simultaneously.
So to achieve the indexer task scheduling goal, address 1. and 2.