configurator standard: make sure there are no "build" activities before activating more in alarms

Otherwise we quickly end up with thousands of activities when one builder has a problem.

(cherry picked from commit 83df786f)

bt5/erp5_configurator_standard/SkinTemplateItem/portal_skins/erp5_configurator_standard/Alarm_buildConfiguratorStandardInvoice.xml

@@ -74,6 +74,11 @@ for builder_id in builder_id_list:\n
   builder = getattr(delivery_tool, builder_id, None)\n
   if builder is None:\n
     continue\n
+  if portal.portal_activities.countMessage(\n
+      method_id=\'build\',\n
+      path=builder.getPath(), ):\n
+    continue\n
+\n
   delivery_portal_type = builder.getDeliveryPortalType()\n
   serialization_tag    = \'build:%s\' % delivery_portal_type\n
   index_tag            = \'index:%s\' % delivery_portal_type\n

bt5/erp5_configurator_standard/SkinTemplateItem/portal_skins/erp5_configurator_standard/Alarm_buildConfiguratorStandardPackingList.xml

@@ -71,6 +71,11 @@ for builder_id in builder_id_list:\n
   builder = getattr(delivery_tool, builder_id, None)\n
   if builder is None:\n
     continue\n
+  if portal.portal_activities.countMessage(\n
+      method_id=\'build\',\n
+      path=builder.getPath(), ):\n
+    continue\n
+\n
   delivery_portal_type = builder.getDeliveryPortalType()\n
   serialization_tag    = \'build:%s\' % delivery_portal_type\n
   index_tag            = \'index:%s\' % delivery_portal_type\n