[FIX] sale: normalize domain is smart

When manipulating domain, this is always better to
normalize them, otherwise we can have strange behavior
when handleing them with `expression.OR` and
`expression.AND`.

For instance:
domain = [('so_line', 'in', [91]), ('amount', '<=', 0.0)]
timesheet_domain = ['&', ('so_line', 'in', []), ('project_id', '!=', False)]

`expresion.OR(domain, timesheet_domain)` will give
['|', ('so_line', 'in', [91]), ('amount', '<=', 0.0), '&', ('so_line', 'in', []),
('project_id', '!=', False)]

And this is not what we attempt.

Closes #24038

addons/sale/models/sale.py

@@ -1183,7 +1183,7 @@ class SaleOrderLine(models.Model):
             on SO lines. This method is a hook: since analytic line are used for timesheet,
             expense, ...  each use case should provide its part of the domain.
         """
-        return [('so_line', 'in', self.ids), ('amount', '<=', 0.0)]
+        return ['&', ('so_line', 'in', self.ids), ('amount', '<=', 0.0)]
 
     @api.multi
     def _analytic_compute_delivered_quantity(self):

addons/sale_timesheet/models/sale_order.py

@@ -175,6 +175,7 @@ class SaleOrderLine(models.Model):
     @api.multi
     def _analytic_compute_delivered_quantity_domain(self):
         domain = super(SaleOrderLine, self)._analytic_compute_delivered_quantity_domain()
+        domain = expression.AND([domain, [('project_id', '=', False)]])
         timesheet_domain = self._timesheet_compute_delivered_quantity_domain()
         return expression.OR([domain, timesheet_domain])