configurator_standard_trade_template: enable "Accept" solver on resource divergences

When changing the resource of the variation, this has a big impact, so we
enable a divergence, mostly to be consistent with the fact that we ask
resolution for quantity divergences: if we ask "we planned for 3 apples,
instead we have 2 apples what should we do ?", it's a bit strange not to ask
anything for "we planned for 3 apples, instead we have 3 carrots"

bt5/erp5_configurator_standard_trade_template/PathTemplateItem/portal_rules/new_delivery_simulation_rule/resource_tester.xml

@@ -18,6 +18,20 @@
               <persistent> <string encoding="base64">AAAAAAAAAAM=</string> </persistent>
             </value>
         </item>
+        <item>
+            <key> <string>categories</string> </key>
+            <value>
+              <tuple>
+                <string>solver/portal_solvers/Accept Solver</string>
+              </tuple>
+            </value>
+        </item>
+        <item>
+            <key> <string>description</string> </key>
+            <value>
+              <none/>
+            </value>
+        </item>
         <item>
             <key> <string>id</string> </key>
             <value> <string>resource_tester</string> </value>

bt5/erp5_configurator_standard_trade_template/PathTemplateItem/portal_rules/new_delivery_simulation_rule/variation_tester.xml

@@ -35,6 +35,14 @@
               <persistent> <string encoding="base64">AAAAAAAAAAM=</string> </persistent>
             </value>
         </item>
+        <item>
+            <key> <string>categories</string> </key>
+            <value>
+              <tuple>
+                <string>solver/portal_solvers/Accept Solver</string>
+              </tuple>
+            </value>
+        </item>
         <item>
             <key> <string>description</string> </key>
             <value>