Add new categories to select constraints in each step of the upgrade
Rename _build to _checkConsistency to follow Constraint API

Also, the logic of all Configuration Items was not changed, but now the changes are applied only if fixit is True.
Remove trailing whitespaces
Add test to simulate the issue with the method TemplateTool.installBusinessTemplateListFromRepository

Using the method try to install Business Templates that are already
installed, the Business Templates is uploaded on ERP5 but not used. It
creates a lot of garbage because in the end you have many bt5s not
installed.
Use fixConsistency because _build method was dropped
inherit Base for reuse methods fixConsistency / checkConsistency
Configurator should follow Constraint API, then fixConsistency method should be enough to do everything
Improve code because is not needed call fixConsistency twice
Remove external method because is not working in slapos environment and calling this is only stopping the intance instead of restart
Add script and extend external method to be possible dump workflow chains to be compared with all configuration defined on Business Templates
add Script Constraint actions, view and actions
Add constraints that can be used in the upgrader
Extend method to be possible filter constraint by contraint_type
Add Business Template with Constraints as a example of bt5 with all configuration required to upgrade
Remove constraint used only to test.

This constraint is not generic enough to be kept
Add test to check a full upgrade
Simplify erp5_upgrader to be possible upgrade any project just enabling the alarms that all Constraints will be called and fixed.

The alarms were renamed to cover each step of upgrader and give the possibility to call each step manually one-by-one. Also, all Scripts that the logic can be done by installing Business Template was removed.
Update change log
Add constraints to be used in tests as example
Improve code to create Active Process in the alarm