mrp: auto_planned state should not be considered as draft

Auto planned movements are not only draft, it could be very useful to take such
movement into account when doing stock optimisations

bt5/erp5_advanced_invoicing/WorkflowTemplateItem/portal_workflow/invoice_workflow/states/auto_planned.xml

@@ -38,9 +38,7 @@
         <item>
             <key> <string>type_list</string> </key>
             <value>
-              <tuple>
-                <string>draft_order</string>
-              </tuple>
+              <tuple/>
             </value>
         </item>
       </dictionary>

bt5/erp5_mrp/WorkflowTemplateItem/portal_workflow/production_order_workflow/states/auto_planned.xml

@@ -39,7 +39,8 @@
             <key> <string>type_list</string> </key>
             <value>
               <tuple>
-                <string>draft_order</string>
+                <string>planned_order</string>
+                <string>future_inventory</string>
               </tuple>
             </value>
         </item>

bt5/erp5_project/WorkflowTemplateItem/portal_workflow/task_workflow/states/auto_planned.xml

@@ -38,9 +38,7 @@
         <item>
             <key> <string>type_list</string> </key>
             <value>
-              <tuple>
-                <string>draft_order</string>
-              </tuple>
+              <tuple/>
             </value>
         </item>
       </dictionary>

bt5/erp5_trade/WorkflowTemplateItem/portal_workflow/order_workflow/states/auto_planned.xml

@@ -39,7 +39,7 @@
             <key> <string>type_list</string> </key>
             <value>
               <tuple>
-                <string>draft_order</string>
+                <string>planned_order</string>
               </tuple>
             </value>
         </item>