base: configure destination_carrier as a destination arrow category

this will have a side effect that Trade Model Path will also consider
destination carrier, like it does with source_carrier.

Not having destination carrier seems not intentional, during the
early days of "new simulation", source_carrier was added but not
destination_carrier, this was commit d487196a (A first idea of how
BusinessPath will look at the end, 2010-05-22)

bt5/erp5_base/CategoryTemplateItem/portal_categories/destination_carrier.xml

@@ -52,7 +52,9 @@
         <item>
             <key> <string>category_type</string> </key>
             <value>
-              <tuple/>
+              <tuple>
+                <string>destination_arrow</string>
+              </tuple>
             </value>
         </item>
         <item>