…nches

Description of the issue/feature this PR addresses:
The current implementation of generating CSR files for EDI doesn't differnetiate between parent companies and branches. ZATCA, however, expects slightly different information depending on whether the company is a branch or a parent.

This also includes a refactor of the tests for l10n_sa_edi.

Current behavior before PR:
The Organization Name, Organization Unit Name, and Organization Identifier of whichever company on the journal were being sent to ZATCA.
You could also Onboard/Re-Onboard a journal in different company.

The unit tests for EDI document generation were primarily using a partner based in the US, which meant that the b2b invoicing main flow was not being properly tested

Desired behavior after PR is merged:

Parent/Standalone Company:
- Organization Name: The name of the company
- Organization Unit Name: First 10 characters of the VAT
- Organization Identifier: The VAT of the company

Branch:
- Organization Name: The name of the parent
- Organization Unit Name: The name of the branch
- Organization Identifier: The VAT of the parent
- Prevent users from posting invoices, credit notes, or debit notes whose invoice company doesn't match the journal company
- The tests are easier to read and they test the b2b flow correctly

opw-4794842

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

Forward-Port-Of: odoo/odoo#221109
Forward-Port-Of: odoo/odoo#213518

Backport of: https://github.com/odoo/enterprise/pull/89358

- Before this commit: The automatic creation of reco model is constrained by company, account and journal. So if the reco model with this config exists then new reco model will not be created.

- After this commit: Now we have removed the constraint entirely. Because we want to have more than one reco model with the same account in it.

- Example: Suppose we have 3 statement lines with 'Rent' as a label in them, and 3 statement lines with 'Location' as a label in them.

  So before this commit when user sets same account on the first two lines with 'Rent' label, will create a new reco model with 
  '{Common substring} - {account code}' as a model name and common substring from labels of both lines will be set as a 
  match_label_param of the model. And then user next set that same account on the first two lines with 'Location' label, will not    
  create a new reco model automatically, because for this config one reco model already exists.
  
   But now after this commit when user sets same account for first two lines with 'Location' label will also create a new reco 
   model automatically with '{Common substring} - {account code}' as a model name and common substring from labels of both 
   lines will be set as a match_label_param of the reco model.

Task: 4876374