slapos_accounting: builder: group movement by specialise

Previously, we has 1 invoice per simulation tree.
But we want to reduce the number of invoice, without using the "aggregate" builder trick

master/bt5/slapos_accounting/SkinTemplateItem/portal_skins/slapos_simulation/SimulationMovement_buildSlapOS.py

@@ -4,13 +4,21 @@ if context.getDelivery() is not None:
 if context.getLedger() != 'automated':
   return
 
-root_applied_rule = context.getRootAppliedRule()
-root_applied_rule_path = root_applied_rule.getPath()
+# group by specialise: the trade condition is the common link betweek every line/cell on a delivery
 
 business_link = context.getCausalityValue(portal_type='Business Link')
 if business_link is None:
   raise ValueError('Movement without business link: %s' % context.getRelativeUrl())
-lock_tag = 'build_in_progress_%s_%s' % (business_link.getUid(), root_applied_rule.getUid())
+
+trade_condition = context.getSpecialiseValue()
+if trade_condition is None:
+  raise ValueError('Movement without specialise: %s' % context.getRelativeUrl())
+
+lock_tag = 'build_in_progress_%s_%s' % (business_link.getUid(), trade_condition.getUid())
 if context.getPortalObject().portal_activities.countMessageWithTag(lock_tag) == 0:
-  business_link.build(path='%s/%%' % root_applied_rule_path, activate_kw={'tag': tag})
-  root_applied_rule.activate(activity='SQLQueue', after_tag=tag, tag=lock_tag).getId()
+  business_link.build(
+    ledger__uid=context.getPortalObject().portal_categories.ledger.automated.getUid(),
+    specialise__uid=trade_condition.getUid(),
+    activate_kw={'tag': tag}
+  )
+  business_link.activate(activity='SQLQueue', after_tag=tag, tag=lock_tag).getId()