### Background

In PR #23171, we provided functionality such that when sending an invoice, if the invoice already exists in SUNAT, we catch the error and retrieve the CDR of the existing invoice.

This was useful in situations where Odoo encounters an exception after the invoice is sent to SUNAT, which leads to an inconsistent state.

However, that PR only implemented this for the IAP service.

In this PR, we extend this functionality to the SUNAT and Digiflow services, so that there also, if the invoice already exists, we retrieve the CDR.

### Implementation Notes
- We refactor the logic for retrieving the CDR if the invoice already exists:
    - previously, the method that sends the invoice checked the error code, and if the code was 1033 or 4000 (document already exists), we would immediately try to retrieve the CDR.
    - now, we have moved this logic to the `_post_invoice_edi` method, which reads the error code that was returned by the function that sends the invoice, and if it is 1033 or 4000, calls the method to try to retrieve the CDR. 
- As a result, the method that sends the invoice (`_l10n_pe_edi_get_status_cdr_iap_service`) no longer needs to know the `serie_folio` of the invoice (which was only needed when retrieving the CDR). In master, we will therefore remove that parameter from the method definition.
- After retrieving the CDR, we check that the date and partner of the retrieved CDR match those of the invoice. If they don't match, this means that the retrieved CDR does not actually correspond to the invoice that was sent. In this case, we don't save the CDR with the invoice and we show the error to the user.

Forward-Port-Of: odoo/enterprise#38224
Forward-Port-Of: odoo/enterprise#30476

Reproduction:
1. Install Accounting, Sale, account_intrastat, sale_intrastat
2. In a Belgium company, go to Sale, make a sale order
3. Choose a customer from the US, edit the shipping address to one in the EU but not Belgium
4. Confirm the order, validate the delivery and create the invoice
5. The Intrastat country on the invoice is empty

Reason: the condition of the initializing of Intrastat country is wrong, should depend on the delivery address.

Fix: Change the condition based on delivery address. This is not an
issue in Odoo 16 because we have a recompute all compute field step.
Nevertheless, this initialization should fw to master for correctness.
However, simply fixing the initialization will conflict with the compute
function's logic. Thus we backport the change in 16 to 14 to have a
clean and more compact compute logic. The computing logic is re-written
for easier understanding.

The step to recompute fields in 16:
https://github.com/odoo-dev/odoo/blob/32bc28aa665c479e31a40afffca2f03f6f2cc805/odoo/api.py#L713-L717
It’s added here:
https://github.com/odoo-dev/odoo/commit/32bc28aa665c479e31a40afffca2f03f6f2cc805

Initial commit of initialization:
https://github.com/odoo-dev/enterprise/commit/bdd258ddfca3401ea4a3dad9f73ac43c791002ba

Fix of the logic in 16:
https://github.com/odoo/enterprise/commit/d96930c706b5e13ec94a4759d2ba0f00b883b9ba

opw-3051881

Forward-Port-Of: odoo/enterprise#38703
Forward-Port-Of: odoo/enterprise#36025

There are currently a performance issue using the search bar of the partner ledger report.  For a report of 1200 partners, with the setting 'Add totals below section' activated, the page will take several seconds (depending on the number of filtered lines) when using the search bar, before displaying the correct lines.
The customer who reported the issue has 5000 partners, it's almost unusable in his case.

The issue is that there's a function that is quite slow, which looks at every children node that matches the search and make sure their parent node is also matched (so you don't see children nodes without their parent).
If all the lines are collapsed, normally there's no children and this function shouldn't consume any time.  But, in v16, for the partner ledger at least, there are one children node per line, which is not displayed, which corresponds to the total of the line (if you activated the setting 'Add totals below section').
-> There's an unnecessary time spent looking for parent nodes of
   children nodes that are not even displayed.

My fix is to select only visible children nodes.

Furthermore, there are some weird behaviors due to this function that will be fixed.
For example, if you type 'total' in the search bar, you will see all the parent nodes.  Because they all have a children node named 'Total%', that you see only if you unfold the node.
Second example, if you unfold a node then collapse it, the html code for the children is still present, so they will be considered for the search but not visible (you will see their parent if one of the children match).

opw-3134212

Forward-Port-Of: odoo/enterprise#38454
Forward-Port-Of: odoo/enterprise#38078