Cycle info in status should not depend on job inputs

The cycle info written to the status file should depend on

* the actual cycles
* the built packages
* the hardcoded cycle breakers in the code

but not on the job inputs, otherwise it will alternate between different states depending on which workflow wrote the status file.