### Contains the following commits:

https://github.com/odoo/o-spreadsheet/commit/5fa5fbb4a [REL] 18.0.3 Task: 0
https://github.com/odoo/o-spreadsheet/commit/09860796e [FIX] pivot: skip cells on manipulated pivot array formulas Task: 4292134
https://github.com/odoo/o-spreadsheet/commit/03d7080d3 [FIX] functions: FILTER with strings and errors Task: 4307604
https://github.com/odoo/o-spreadsheet/commit/eb4c13091 [FIX] charts: do not show zero values in pie charts Task: 4277144
https://github.com/odoo/o-spreadsheet/commit/3eac11e86 [FIX] index: export chart translation terms Task: 3978443
https://github.com/odoo/o-spreadsheet/commit/262b1bc2a [FIX] tests: remove WAIT funtion Task: 4306250
https://github.com/odoo/o-spreadsheet/commit/70f58fa2d [FIX] tests: bad separator in xlsx export Task: 4306250
https://github.com/odoo/o-spreadsheet/commit/ec41486b9 [FIX] tests: remove async function export test Task: 4306250
https://github.com/odoo/o-spreadsheet/commit/c78551c57 [FIX] xlsx: convert #REF at export to xlsx Task: 4207052
https://github.com/odoo/o-spreadsheet/commit/bebac5f29 [FIX] parser: inconsistent handling of #REF Task: 4207052
https://github.com/odoo/o-spreadsheet/commit/c53e76933 [FIX] charts: correct stacked checkbox label Task: 4251670
https://github.com/odoo/o-spreadsheet/commit/5ebba297c [REM] charts: clean createLineOrScatterChartRuntime Task: 0
https://github.com/odoo/o-spreadsheet/commit/d3a2181b7 [FIX] charts: fix trend line for datetime Task: 0
https://github.com/odoo/o-spreadsheet/commit/69a8602cd [FIX] chart: missing checkbox label for combo chart Task: 4283173

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: Mehdi Rachico (mera) <mera@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>

The function `_exclude_tax_group_from_tax_totals_summary` does not exist. It should be `_exclude_tax_groups_from_tax_totals_summary` instead.

This is the same issue for the l10n_cl and l10n_ar module since it's just a call to a non-existent function.

### Steps to reproduce:
- Install the l10n_ar module
- Create an invoice with the document type set to "Invoice C"
- Add a line that includes a tax
- Try to print using the "PDF without payment" button

### Traceback:
```
File "/Users/louis/Development/odoo_src/core/odoo/odoo/addons/base/models/ir_qweb.py", line 600, in _render
  result = ''.join(rendering)
           ^^^^^^^^^^^^^^^^^^
File "<778>", line 107, in template_778
File "<778>", line 89, in template_778_content
File "<778>", line 77, in template_778_t_call_0
File "<1056>", line 2228, in template_1056
odoo.addons.base.models.ir_qweb.QWebException: Error while rendering the template AttributeError: 'account.tax' object has no attribute '_exclude_tax_group_from_tax_totals_summary' Template: l10n_ar.report_invoice_document
Path: /t/t/div[2]/div/div[4]/div[1]/div[1]/div/table/t[1]/t[2]
Node: <t t-set="currency" t-value="o.currency_id"/>
```
opw-4253265

[FIX] account_iso20022: Don't report 'SEPA' as Service Level in ISO20022 files

'SEPA' used to be the default for SvcLvl files, which meant even non-SEPA files would have it set to 'SEPA', unless they explicitly overrode the function defining the value of the node. This commit fixes this, by not setting any value to SvcLvl by default, and overriding for SEPA payments.

=========================================================

[REF] account_iso20022: compute BIC tag depending on the payment method consistently

The CdtrAgt node did not compute the tag of its BIC node in the same way as the DbtrAgt node, calling the dedicated helper. Because of that, it required a bit more payment method-specific code in SEPA, so that BIC becomes BICFI in the latest version. This commit removes that and calls the appropriate helper everywhere.

==========================================================

[IMP] account_iso20022: Don't put 'SCT' in InstrId anymore

Before this commit, each payment's InstrId always contained 'SCT' (unless a memo was set on the payment), standing for "SEPA Credit Transfer". For non-SEPA ISO20022, this did not make sense. Since this having this additional info in the field has not additional informative value anyway, we simply remove it.

==========================================================

[FIX] account_iso20022: fix batch payments' error check

'posted' state does not exist on payments anymore. Anyway, this check was useless. Though, it prevented any of the error checks to run.

Also, a condition had been mistakenly removed in the handling of payments with a too big amount.


[IMP] account_iso20022: proper check on maximum amounts

SEPA Credit Transfer documentation gives a maximum of 999,999,999.99 € to instructed amounts (https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2023-11/EPC132-08%20SCT%20C2PSP%20IG%202023%20V1.1.pdf page 101). Swiss ISO 20022 uses 9,999,999,999.99 instead (https://www.six-group.com/dam/download/banking-services/standardization/sps/ig-credit-transfer-sps2024-2.1.1-en.pdf, page 52).

The check we ran before this commit was wrong. It checked 11 characters (coma included), while it's actually not included, for payments in EUR, and added another limit of 15 characters for other amounts. We relax it to put the proper restrictions when we know them, and not enforce another when we don't.

TO REPRODUCE
===========
1. Create an appointment with users A and B
2. ...using 'no picture' and 'user then time'
3. go to front end
4. pick a date D both users have slots in
5. go to next month
6. change user in the dropdown (or change TZ)
7. slots appear for day D in previous month

ISSUE
=====

When selecting an other resource or user in the dropdown in resource_time mode, even if the selected one has no available slot for the current month, slots will appear in the slot list, corresponding to the first availability overall.

This leads to a very strange mismatch between the calendar dates and the slots. The user may select a slot and book for a month they do not currently see on the calendar.

SOLUTION
========

Now, we will select the previously selected date if it is in the current month and has slots. Otherwise we select the first day with slots in the currently displayed month (NOT overall). This way, the day is selected and displayed as so in the calendar. The slots match that day. If no availability exist for the current month, we do not click on any day, and show no slots.

Task-4169513

### Steps to reproduce:

- Create 2 storable products: Final product (FP) and Component (COMP)
- Put 10 units of COMP in stock
- Create a Bill of Material for FP:
  - raw move: 10 x COMP
  - 1 operation: "Register COMP"
  - Add an instruction on your operation:
    - type: "Register consumed component"
    - Product To Register: COMP
- Create and confirm an MO for 1 Unit of FP
- Go to the shopfloor > "Register COMP"
- Change the quantity to 3 > Validate
#### > Go back to the MO the quantity of the raw move is still 10

### Cause of the issue:

Clicking on "Validate" as well as on "Continue consumption" will trigger a call of the `_next` method with `continue_production=False` and `True` respectively:
https://github.com/odoo/enterprise/blob/e86b97f57e2388b3b65326cecedd3c14ca02ddb1/mrp_workorder/models/quality.py#L346-L352 However, if you underconsume, a new move ine will be created for the remaining quantity in both cases and it should only when you `Continue consumption`.

### Note:

If you underconsume, and change the quantity of the raw move without changing its original demand. As such, its state will itself change. Hence, if you come back to the MO, the reservation sate of the MO will be recomputed and be updated from assigned to confirmed. However, as the raw move is picked it should not alter the reservation state of the MO anymore:
https://github.com/odoo/odoo/blob/9918e8f3d627f3c52238d6b04bcd15c05d34e40c/addons/mrp/models/mrp_production.py#L613 This is the purpose of the community PR.

opw-4216910

StockMove.date does not represent the Scheduled date when the move is Done, but the date it was validated. Hence, if the move was validated outside the period it was made for, it will be accounted for in the future period.

To reproduce, you can:
- Create a subscription with a start_date in the past, so that today's date is in the SECOND period: Ex: Today = "2024-11-01"
    * Recurring plan: Monthly
    * Start Date: "2024-10-01"
- Trigger the cron to invoice & deliver the FIRST period ("2024-10-01" -> "2024-10-31").
- Validate the first period picking => "Scheduled Date" becomes the done date: "2024-11-01"
- Trigger the cron to invoice & deliver the SECOND period ("2024-11-01" -> "2024-11-30"). => Second period picking is NOT generated, because the first period picking was interpreted as belonging to the second period.

---

Test result before fix:
```
2024-11-07 13:44:54,695 34298 ERROR oes_17_test_sss odoo.addons.sale_subscription_stock.tests.test_sale_subscription_stock_order: FAIL: TestSubscriptionStockOnOrder.test_picking_done_in_another_period
Traceback (most recent call last):
  File "/home/odoo/projects/odoo-src/multiverse/src/17.0/enterprise/sale_subscription_stock/tests/test_sale_subscription_stock_order.py", line 543, in test_picking_done_in_another_period
    self.assertTrue(bool(second_picking))
AssertionError: False is not true
```

OPW-4280155

Version: 16.0+

Issue:
When we make commission on a subscription sale order, 
the subscription end and start dates are not passed through the order lines -> invoice lines and 
we run into an error when trying to create the corresponding purchase order.

Purpose of this PR:
If there are no subscription dates on the invoice lines 
then we do not calculate the length of the subscription in months and 
instead create the purchase order line description just as the commission for the corresponding subscription.

Steps to reproduce on runbot:
install partner_commission
set up a subscription with a referrer and a commission plan create invoice for the subscription
try to register the payment for the invoice
error raised regarding a max function with no args

Notes:
looking to investigate further why the subscription dates are not passed from 
the subscription to the order lines to the invoice lines

in 17.0+ field name is changed from `subscription_end_date` to `deferred_end_date` (same for `start` date),
will have to adjust in fw ports

opw-4240937

Forward-Port-Of: odoo/enterprise#73428