This update resolves an issue where the LU reports were incorrectly showing only the first product with a missing internal reference. The change ensures all products with missing internal references are now displayed, providing a more accurate and complete report for Luxembourg accounting. This aligns with reporting requirements and improves data accuracy.

This is one of several commits fixing the FAIA xml export.

The internal reference must be set for all products reported in the FAIA report. When there are multiple products missing this field, our previous code only reported the first ID to the customer. This commit shows the customer all incorrectly configured products.

opw-5427296, opw-6113665

This update corrects a technical issue that could inadvertently transmit payroll data in non-production (test) environments. This change ensures that sensitive payroll information remains isolated to testing, improving data security and preventing potential errors. It’s a routine maintenance fix to maintain the integrity of our payroll system.

This update corrects a bug in the l10n_lu_reports module that caused incorrect calculations of debit and credit amounts in reports. Specifically, it addresses a situation where negative price units resulted in invalid report totals. This ensures accurate financial reporting and avoids validation errors.

This is one of several commits fixing the FAIA xml export:
- #113452
- #113455
- #113846
- #113720

When an invoice line has a negative `price_unit`,  the `Invoice/Line/InvoiceLineAmount/Amount` element has a negative value. This causes validation errors when comparing the total debit or credit values (such as `SalesInvoices/TotalDebit`) to the individual amounts, as the sum of individual "debit" lines will include some
credit amounts and vice versa.

Solution: record if the line is actually a debit or a credit, then use the absolute value of the balance in the Amount
element.

opw-5427296
[Link](https://www.odoo.com/odoo/unassigned-tasks/5427296)

This update fixes a misleading warning that appeared when generating payslips, specifically related to contract dates overlapping with payslip periods. The change improves the user experience by removing the warning when a contract partially overlaps with a payslip, aligning with the behavior in version 19. This ensures accurate payslip generation without unnecessary alerts.

Bug reproduction:
    1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well)
    2 - Create an employee and make its contract from 01-01-2025 to 05-03-2026 (DD/MM/YYYY) format.
    3 - Generate payslip for March, the warning of "The period selected does not match the contract validity period" popups.
    4 - But we do not want that, even though there is 1 overlapping day in contract with payslip we can continue.

Bug cause:
    1 - In >= v.17 (not in v.19), there was a warning, when the contract dates do not fully contains the payslip dates, the warning was appearing.
    2 - In v.19 it is not the case, when there is a contract that overlaps at least one dat of the payslip then we are fine, if no overlap then no contract on payslip warning should appear

Bug solution:
    1 - I replaced old warning "The period selected does not match the contract validity period" with the one in v.19 "No running contract over payslip period"

Tests:
    1 - There was a unit test about old warning (test_payslip_warnings), I changed that parts.
    2 - I added further steps to the existing test about the new warning that should appear (No running contract over payslip period)

Last Test Update:
    1 - I noticed that contract date changes was not affecting the warning appearance directly
    2 - Unit test is expanded with contract date change and observing the warning appearance

Note: Implemented feature: need to check what happens after v.17, should be removed in v.19 latest, maybe before as well.

task - 6006693

This update optimizes the Google Calendar integration by preventing unnecessary cache invalidations when events are updated. The changes streamline the system's data writing process, improving performance and reducing potential delays. This results in a smoother user experience.

When a google event is updated, the cache is invalidated. This is not necessary as the event google_id didn't change.

Also, slightly simplify the ormcache since there is a single call with active_test=False