Original PR description

The outdated page watcher checks whether bus notifications were missed when the bus reconnects after an unexpected disconnection. To do so, it checks if the last known notification id is still in the bus table.

However, it relies on the main tab's last received notification which might not be available when the main tab didn't receive notifications after being elected.

To fix this issue, this commit uses the global last notification stored in the local storage to ensure every tab has access to it.

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

Original PR description

Versions
--------
- 18.0+

Steps
-----
1. Create a service product that creates a task;
2. add product to an order;
3. add an extra description to the sale order line;
4. confirm the order;
5. go to the task.

Issue
-----
The name of the sale order item linked to the task displays the product name instead of the extra line description.

Cause
-----
As 18.0, the first line of the sale order line name is always the product name. In earlier versions, the product name was only used as a fall-back value when no extra description was added to the line.

Solution
--------
Account for the guaranteed addition of the product name in the SOL name, and instead use the second line for the display name if it exists and is non-empty, else fall back on the product name as intended.

opw-4634149

Original PR description

Writing the account code is restricted on l10n_de accounts. Odoo checks that the code we write is different from the old one, and if so it checks of there are already some entries for that accounts. If any of the condition is met, the write is prevented.

When we try to map an account from another company to a l10n_de company, the _inverse_code function from the account mapping will try and update the account code in the other company, as the code is company dependent.

The issue is that we check that the l10n_de code remains the same, even if we are in another, non l10n_de company.

This PR adapts the check to l10n_de account to only check the code if we are writing it from the l10n_de company.

opw-4711417

Original PR description

Steps:
Set enable_formatting to false on an Integer field (ex. ID).
Turn the ID column to be visible in subtask list view.
Add a new record using list view.

Issue:
The ID field displays false till saved.

Reason:
enable_formatting: false was used to remove regional formatting 
 (e.g., thousand separators) for the ID field. But this also disabled all other
formatters, including null value handling, resulting in false value in ID field.

Fix:
Introduced a new option skip_thousands_separator under the IntegerField
formatting logic.When enabled, it disables only the thousands separator 
while preserving other formatting behaviors.

task-4700791

Original PR description

Adding a condition to match contry to CO when looking for NIT latam ID type.
Otherwise, adding another ID type named 'NIT' for a different country causes
the search to return both, resulting in a traceback.
Related to https://github.com/odoo/odoo/pull/189687

task-4318265