Original PR description

[FIX] l10n_ch_hr_payroll_elm_transmission: fix avs test for faketime build

Bug reproduction:
    1 - v.17->run test_generic_avs_deductions test with faketime 2027-01-01 12:00 UTC->test fails

Bug cause:
    1 - In the test, compute_sheet()->_get_payslip_lines->_compute_rule->_get_avs_rates is called
    2 - There is a line like that if line.date_from <= target and (not line.date_to or target <= line.date_to)
    3 - I looked to avs_line_ids = fields.One2many(default=_get_default_avs_line_ids)
    4 - In _get_default_avs_line_ids -> 'date_from': fields.Date.today().replace(month=1, day=1) date_from is calculated like that -> when the year is 2027, the date_from is 2027-01-01 and it is bigger than the target in the test.

Bug solution:
    1 - I used @freeze_time("2026-02-28") in my test to prevent this behavior.

Runbot Error Link: https://runbot.odoo.com/odoo/runbot.build.error/240992

task - 6018940

Original PR description

odoo/odoo#255054 saved the chrome log at the end of a tour (logging that as `INFO` on success and `RUNBOT` on failure). However as it turns out there are a few issues with that:

1. In case of chrome error during termination (`stop`), those errors can not be in the log, since the log was already saved.
2. Chrome buffers logs a lot more than anticipated, and because `--v=0` logs are a lot less chatty than `--v=1` the logs routinely show essentially nothing (a few tour steps are logged then nothing).

Also make `stop` a bit more resilient to chrome issues:

- handle errors around ws shutdown
- wait for chrome to shut down before we try to remove the data directory
- also add a fallback *killing* chrome if it doesn't seem to be shutting down

Forward-Port-Of: odoo/odoo#256061

Original PR description

Currently, the tax for "VAT Sale of service outside EU 0%" has the 0% EU RS name and is associated with the se_39 grid. Since it is for outside the EU, it's name should be 0% EX RS and the grid should be se_40

opw-5798152

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

Original PR description

In some cases, the users may have invoices with the same product, price unit, and discount on multiple lines. When they create refunds from such invoices, the lines ids matching algorithm would fail because it would match the first matching line over and over again. Also, lines should not match based on line label, as it can be modified in the refund.

This commit solves these 2 issues by
1) Preventing matching an invoice line more than once with refund lines
2) Preventing matching based on line label

The new algorithm finds the best match for a refund line from the invoice lines with the following criteria:
1) same product
2) same unit price
3) same discount
4) invoiced quantity should be at least equal to the refunded quantity 5) invoice line should not be matched before
6) from the lines that match previous criteria, we pick the one with the minium quantity

task-6004207