sale_stock_available_to_promise_release: improve '_get_next_replenishment_date' perf

Checking ongoing states instead of finished ones (done and canceled) helps
PostgreSQL to perform the filter on far less lines (done lines are
increasing a lot over time), speeding up the query to get the next
replenishment date.

Author: sebalix

sale_stock_available_to_promise_release/models/product_product.py

@@ -12,7 +12,17 @@ def _get_next_replenishment_date(self):
         move_line = self.env["stock.move"].search(
             [
                 ("product_id", "=", self.id),
-                ("state", "not in", ["done", "cancel"]),
+                (
+                    "state",
+                    "in",
+                    [
+                        "draft",
+                        "waiting",
+                        "confirmed",
+                        "partially_available",
+                        "assigned",
+                    ],
+                ),
                 ("picking_type_id.code", "=", "incoming"),
             ],
             limit=1,

sale_stock_available_to_promise_release/models/stock_move.py

@@ -11,3 +11,6 @@ class StockMove(models.Model):
     sale_date_expected = fields.Date(
         "Delivery Date", related="group_id.date_expected", store="True"
     )
+    # Add index on picking_type_id to speedup '_get_next_replenishment_date'
+    # method on 'product.product'
+    picking_type_id = fields.Many2one(index=True)