the return value of _load_records is defined as

:return: the records corresponding to ``data_list``

which means the

len(_load_records(data_list, ..)) == len(data_list)

while in some corner cases it is not satisfied

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

This 1st commit is the first approach to fix the problem (check diff for the first commit)

since during `_load_records`, each `data` in `data_list` is modified with key 'records' (fixed: in some corner cases, data['records'] won't be assigned and may case KeyError when return). I think it is OK to add one more key 'state'/'modified' in the data as a hack to identify data for new created records.

I personaly think the name `ignore_duplicates` is quite confusing. My gut feeling is either during or after `_load_records` there will be duplicated records or xml_Ids and they are acceptable for sake of `ignore`. But I haven't found a better name.

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

The 2nd commit is the second approach to fix the problem (check diff for the whole PR)

This approach uses one extra query per model in `_load_data` for account
to filter out data for existing records before `_load_records` to avoid
modifying `base`.

NOTE: previously `ignore_duplicate` won't update existing records but can update
their xml_ids, not sure if it is a side-effect or designed feature.


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

**Steps to reproduce:**

Use a Colombian company.
Configure DIAN / Carvajal (company, product, and supplier) as per documentation. Change the language to Spanish (LATAM).
Create a new Purchase Order using the supplier and the product:
- Receive the product.
- Create the Vendor Bill:
   - Change the Journal to the DIAN Support Documents journal and set the date.
   - Using the actions, print the invoice (even without payment) and look at the document title.

[![Capture d’écran 2025-01-09 à 10 48 55](https://github.com/user-attachments/assets/77781193-ef93-4611-9e42-83289b5a8298)](https://github.com/user-attachments/files/18359586/SEDS_2025_01_0014.pdf)

- Create a Credit Note:
   - Using the actions, print the credit note (even without payment) and look at the document title.

[![Capture d’écran 2025-01-09 à 10 49 14](https://github.com/user-attachments/assets/1894bc76-820c-4283-9d42-b4cc0e75ef39)](https://github.com/user-attachments/files/18359584/RSEDS_2025_01_0009.pdf)

---
**Issue:**

DIAN vendor bills and vendor credit notes display `Factura de proveedor` and `Nota de crédito de proveedor`.

---
**Expected:**

DIAN vendor bills and vendor credit notes should display `Documento Soporte` and `Nota de Ajuste del Documento Soporte`.

---
**Cause:**

Vendor bills and credit notes are not managed by Colombian's EDI nor DIAN modules but only by the Account module.

---
**Fix:**

Add DIAN-specific `Vendor Bill` and `Vendor Credit Note` translations. Manage the title replacement in the generated file if the PDF generation is done by the DIAN module.

[![Capture d’écran 2025-01-09 à 10 41 57](https://github.com/user-attachments/assets/cc69915e-d94d-4e96-ba71-2266e05e2a9e)](https://github.com/user-attachments/files/18359493/SEDS_2025_01_0013.pdf)

[![Capture d’écran 2025-01-09 à 10 42 59](https://github.com/user-attachments/assets/40d17e0b-488b-4ba6-9d80-76805f54f234)](https://github.com/user-attachments/files/18359499/RSEDS_2025_01_0008.pdf)


---
**Task References:**

opw-4423439
opw-4433918