This started with noticing that the way the rejected invoices were handled in the response changed.  Before, it was handled as a json in a string in a json, now it is directly in a json and most importantly, when the invoice is considered "rejected", ZATCA returns it as a 400 error.

This made us check further and e.g. when we resend a rejected, the issue time is supposed to be the same, so the logic of the confirmation time was changed so it still behaves the same in pure l10n_sa, but if you have a rejected one, it won't be overwritten when you confirm the invoice again.

We also added the rejected invoice as an attachment for auditibility and put a mechanism in place to avoid the user to delete it.

When we have a 400 error, the chain index is reset (ICV field), because then, when we send a new one, it will have a new ICV. The goal for auditibility is that each chain index corresponds to one submission of an invoice.  E.g. if we have a timeout, the chain index is kept and we are supposed to check that invoice first before proceeding with other invoices because we do not know whether the invoice was submitted or not, so we need to retry and that way it might override the existing ICV with ZATCA.

We do the same for 401+ errors just to make sure that one ICV equals one invoice (although here, we could reset the sequence after we get the error if it causes too much trouble)

The error/warning messages were a bit updated to clearly indicate the HTTP status code and the error code from ZATCA in bold and to avoid putting Python dicts, but nicely formatted messages.

opw-4689622

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Forward-Port-Of: odoo/odoo#205671

Otherwise, it will create massive domains, which may exhaust the memory available to PG:

```
 Traceback (most recent call last):
   File "/home/odoo/src/odoo/18.0/odoo/tools/safe_eval.py", line 397, in safe_eval
    return unsafe_eval(c, globals_dict, locals_dict)
   File "ir.actions.server(364,)", line 5, in <module>
   File "/home/odoo/src/odoo/18.0/addons/stock/models/stock_orderpoint.py", line 257, in action_open_orderpoints
    return self._get_orderpoint_action()
   File "/home/odoo/src/odoo/18.0/addons/stock/models/stock_orderpoint.py", line 500, in _get_orderpoint_action
    qty_by_product_loc, dummy = self.env['product.product'].browse(product_ids)._get_quantity_in_progress(location_ids=location_ids)
   File "/home/odoo/src/odoo/18.0/addons/purchase_stock/models/product.py", line 50, in _get_quantity_in_progress
    groups = self.env['purchase.order.line'].sudo()._read_group(domain,
   File "/home/odoo/src/odoo/18.0/odoo/models.py", line 1989, in _read_group
    row_values = self.env.execute_query(query.select(*groupby_terms.values(), *select_terms))
   File "/home/odoo/src/odoo/18.0/odoo/api.py", line 978, in execute_query
    self.cr.execute(query)
   File "/home/odoo/src/odoo/18.0/odoo/sql_db.py", line 572, in execute
    return self._cursor.execute(*args, **kwargs)
   File "/home/odoo/src/odoo/18.0/odoo/sql_db.py", line 354, in execute
    res = self._obj.execute(query, params)
 psycopg2.errors.SyntaxError: memory exhausted at or near "("
LINE 1: ...((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((...
                                                             ^
```

upg-2461663

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

Forward-Port-Of: odoo/odoo#202065

Steps to reproduce:
Using POS configs in french company with l10n_fr_post_cert module installed.
- Checkout 1: Prepare an order with several lines held in stock, to ensure that Odoo takes sufficient time for payment.
- Cash desk 2: Prepare an order
- Cash-desk 1: Start order payment.
- Cash-desk 2: Start order payment while cash-desk 1 is still paying.

Issue:
When writing 'paid' in a pos_order the l10n_fr_post_cert sets the l10n_fr_pos_cert_sequence_id field. A competition error occurs on cash desk 2 during payment: could not obtain lock on row in relation “ir_sequence”. The odoo.service.model retries to create the order and since the ir_sequence of pos_config used in the pos_order name is not set to "no_gap", the pos_order names have a gap equal to the number of retries.

Task-4708543

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Forward-Port-Of: odoo/odoo#205935

### Issue:

Although Fedex's API shoud accept GBP's UK currency for rate requests, you will raise a `CURRENCY.TYPE.INVALID` error from Fedex if you try to get the shipping rate for an order whose currency is GBP.

### Steps to reproduce:

- Install UK accounting and select UK's company: the currency will be GBP
- Install and set up Fedex Integration
- Configure the Fedex in the delivery method, FEDEX_YOU_PACKAGE and Fedex priority for package type and service type
- Create a sale order, add shipping and get the shipping rate for your set up fedex UK.
#### > Fedex request error: `CURRENCY.TYPE.INVALID`

### Cause of the issue:

The currency used in the fedex request is the currency of the order: https://github.com/odoo/enterprise/blob/07845988daad911b10de3b7199b81cc4ed3cfba9/delivery_fedex_rest/models/delivery_fedex.py#L133-L141 that is GBP, however since 44e32359bb79eed08a41861e155c98f664c6d09a we do not automatically convert the GBP currency in UKL. Since Fedex API does not seem to support the GBP we raise the error.

### Fix:

We should use the currency conversion available between GBP and UKL.

opw-4712354

Forward-Port-Of: odoo/enterprise#83388