erp5_upgrader: show all inconsistencies on activeSense
It goes a bit against the activeSense principle of being fast to know if something needs to be fixed, so it can run often. But the upgrade alarms do not run automatically.
From experience, ERP5 upgrades are sensitive processes, and we want to know exactly what's happening. Some upgrade constraints could potentially put the service down (like an alter table on a huge catalog). So it's better for administrators to see everything that will / need to be fixed before it happens for real.
The constraint on speed now falls on the consistency checks themselves, which anyway also take the "fixit" parameter.