When changing the expense policy of an expense product, the
compute of analytic distribution of all expenses linked to the product
is triggered.

Steps:

- Have an expense product X with expense policy 'at_sales'
- Create several expenses with an expense product X and  any analytic account
- Create an analytic distribution model that link the expense account of
  X with a specific analytic account AA
- Create a new expense for product X, the analytic account AA should be set
  from the distribution model
- Go to the form view of product x and change the expense policy to
  'cost'
- Go back to the expense list view
-> All expenses having the product X have the AA account

Cause:

`sale_order_id` has been added to the `depends` of `hr_expense._compute_analytic_distribution`
by 2b3bf5e0fe31d4b4ef6b487da493657f695b14e1 but this wrong since we have
the `sale_expense._onchange_sale_order_id` that add the
`analytic_dostribution` field to the fields to be computed.
The compute is triggered since we change `product_id.expense_policy`,
which triggers the `_compute_can_be_reinvoiced` which triggers
the `_compute_sale_order_id`

Fix:

With this commit, we emove the depends on the compute and we also adapt
`test_compute_analytic_distribution_expense` in a way that it triggers the onchange
as we do in the original flow.

opw-4998899

In this bug, when there are multiple warehouse, and a warehouse is supplied by another one, the security lead time is repeated in calculations.

To reproduce the bug:
1- Create a db with, stock, mrp, sale installed.
2- Unarchive `MTO` route.
3- Set `Security Lead` Time in Setting.
4- Create two warehouses wh1, wh2.
5- In wh1, set `Manufacture to Resupply` to True.
6- In wh2, set `Manufacture to Resupply` to False and make it resupply from wh1.
7- Create a product and track inventory.
8- Create a BOM for the product.
9- Enable `Manufacture`, `MTO`, `wh2: Supply Product from wh1` routes for the product.
10- Create a new Quote for the product and in the Delivery, select `wh2` as the warehouse. Confirm the Quote.
11- Open MO. Security lead time is considered twice in dates calculations which is mistake.

To solve this issue, we must call `_get_dates_info` only once. The current condition might be True more than once for multiple moves. We should also check that it is not True for next moves which otherwise means the security lead time is already effected.

This issue is reproduced because this condition is not sufficient to ensure it is called once:
https://github.com/odoo/odoo/blob/c0a7b51c9e14d29cefa96c29dd716b7aec698818/addons/stock/models/stock_move.py#L1656-L1657

The above condition is written to ensure we are adding the delay only when move location is warehouse stock location.

This cause problem in multi-warehouse because we have this case that move location is warehouse stock location once for wh1 and once in wh2.

To solve this issue, we make sure the call `_get_dates_info` doesn't affect when the move has rules with src location in warehouse stock location.

related: #112325

opw-4889642

### Contains the following commits:

https://github.com/odoo/o-spreadsheet/commit/7e6662c53 [REL] 18.0.44 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)
https://github.com/odoo/o-spreadsheet/commit/9ca5b656c [FIX] Menu: Fix item text truncation [Task: 5072649](https://www.odoo.com/odoo/2328/tasks/5072649)
https://github.com/odoo/o-spreadsheet/commit/6a7eee11b [FIX] xlsx: remove useless warnings on import [Task: 5075112](https://www.odoo.com/odoo/2328/tasks/5075112)
https://github.com/odoo/o-spreadsheet/commit/e81d09c1e [FIX] xlsx: `=undefined` when importing array formula [Task: 4812508](https://www.odoo.com/odoo/2328/tasks/4812508)
https://github.com/odoo/o-spreadsheet/commit/71808b2b1 [REV] xlsx: make import verbose [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)
https://github.com/odoo/o-spreadsheet/commit/44df57169 [FIX] clipboard: insert cells bugged with array formulas [Task: 4938311](https://www.odoo.com/odoo/2328/tasks/4938311)

Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com>
Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com>
Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com>
Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com>
Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com>
Co-authored-by: Ronak Mukeshbhai Bharadiya <rmbh@odoo.com>
Co-authored-by: Florian Damhaut (flda) <flda@odoo.com>
Co-authored-by: Rémi Rahir (rar) <rar@odoo.com>
Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com>
Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>

## Versions:
16.0+

## Issue:
After confirming a Sales Order (SO), loyalty points are incorrectly calculated when applying additional promotions. This causes only one reward to be applied instead of all eligible ones.

## Cause:
When the SO is confirmed, the cost in points for each line is retrieved and deducted to compute remaining available points. However, when promotions are re-applied, the system re-evaluates the total cost of the SO and deducts the points again, effectively double-counting the same lines.

## Steps to reproduce:
- Set up a `Discount & Loyalty` promotion program:
  - 2 points granted per purchase (minimum $0).
  - Rewards:
    - 5% discount on "Simple Pen" (costs 1 point).
    - 10% discount on "Whiteboard Pen" (costs 1 point).
  - Create a Quotation with "Simple Pen" and "Whiteboard Pen".
  - Confirm the Quotation into a Sales Order.
  - Apply promotions:
    - The first reward applies correctly
    - The second reward does not apply

opw-4753472

Forward-Port-Of: odoo/odoo#211342

steps to reproduce:
-------------------
1. Install `l10n_cl`.
2. Create a new company and set Chile as the country.
3. Go to Accounting > Configuration > Journals.
4. Create a journal with type Purchase and enable Use Documents.
5. Go to Accounting > Vendors > Bills and create a bill.
6. Print Invoices / Invoices without payments.

issue:
------
The customer and company data are swapped (interchanged), and It is wrong from vendor bills point of view.

solution:
---------
The l10n_cl reports layout should only be applied to: 
- out_invoice or out_refund
- or when l10n_latam_document_type_id = (46) Electronic Purchase Invoice

**Before:**
<img width="762" height="425" alt="image" src="https://github.com/user-attachments/assets/e042485b-5d82-455f-9f34-03a0a9cdf5cc" />
**After:**
<img width="770" height="624" alt="image" src="https://github.com/user-attachments/assets/c5d09e58-bcf0-48ab-a0ae-0e37c0473a67" />



opw-4937097

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#224454

Currently, an error is encountered when a financial report contains a line with a formula that results in a division by zero.

**Steps to Reproduce:**
- Install **accountant, account_reports module** (without Demo).
- Navigate to Accounting>Reporting>Profit & Loss
- Enable Developer mode, Click on the Edit(Gear Icon) smart button, then click Create to add a new line.
- In the new expression line, set the following:
>- Computation Engine: Aggregate Other Formulas
>- Formula: NEP.balance / REV.balance
- Save the new report line.
- Reopen Profit & Loss, Report error will encounter

**Error:**
`ZeroDivisionError: float division by zero`

**Root Cause:**
At [1], in the `else` block, the case of a potential ZeroDivisionError is not handled properly, causing this issue.

[1] https://github.com/odoo/enterprise/blob/770582d4c85629568b2e64f58651f59a9a9a5f86/account_reports/models/account_report.py#L3549-L3556

**Solution:**
This commit prevents the error by ensuring that the case of a potential zero division is handled properly.

Sentry-**6720835207**