This update removes obsolete code from the Chilean electronic invoicing point-of-sale module after customer editing was moved to Odoo's standard interface. It reduces maintenance overhead without changing the business workflow for users.

We have recently replaced the custom form for editing res_partner records that was used in pos with the default `view` component from web. ( commit 2c068a719617314a3c7c875af7f9027d0531652c )

In this commmit we remove code that is now useless.

The spreadsheet pivot table infrastructure has been reorganized so key plumbing can live in the shared o-spreadsheet project. This prepares Odoo for future spreadsheet pivot table capabilities while keeping existing Odoo tests in place to protect current behavior.

This commit is the enterprise counterpart of https://github.com/odoo/odoo/pull/159259.

This commit prepares the ground to the introduction of the spreadsheet
pivot table in github.com/odoo/o-spreadsheet. It's basically a move of
the plumbing necessary to make a pivot works from odoo codebase to
o-spreadsheet codebase.

A note on this commit:

- Tests are kept in Odoo

Moving tests would require to make a dummy pivot in o-spreadsheet, which is
not ideal. Let's write tests during/after the introduction of spreadsheet
pivot.

Task: 3748583

Point of Sale formatting logic has been streamlined so amounts and related values are handled through one consistent method. This reduces duplication behind the scenes and helps keep receipts, payment screens, and localized POS flows more consistent.

Before, we were using multiple functions in order to format the numbers.
This pull request allow us to use a single method format which take for arguments:

The Type of the format you want to apply
The value
The different options available for the given type

Community pr: https://github.com/odoo/odoo/pull/85770

This change simplifies how CRM leads and helpdesk ticket conversion handle partner matching by removing an unnecessary shared component. It should not change day-to-day workflows, but it makes the underlying code easier to maintain and align with the wider CRM refactoring.

This refactoring commit follows the one from Community (From PR https://github.com/odoo/odoo/pull/35864) :

Because it seems to be a mixin for unnecessary fields (redefined in inheriting
models) holding a utility method we could move on lead model.

- move _find_matching_partner to crm.lead
- move action into crm.lead2opportunity.partner
- move partner_id to each model that inherits crm.partner.binding

Task ID: 2056759

This change removes an older phone validation component and standardizes the VoIP module on the newer shared phone handling approach. It reduces duplicate technical paths, making future maintenance more consistent without changing the expected business workflow.

…thread.phone

This commit 7e8a02cd6e9f08e5ff45db804b357bc3537ff1f6
introduced the 'mail.thread.phone' mixin.

The 'phone.validation.mixin' became at that point a less powerful version of it.

This commit cleans the code and completely removes the 'phone.validation.mixin' to lessen entry
points of phone validation methods and reduce mixins amount.

Task#2092372

Engineering change orders and quality controls have been adjusted to work with the newer calendar view experience. This keeps planning and scheduling screens consistent with the latest interface changes, with minimal direct business impact.

This update removes obsolete internal markers that are no longer needed because Odoo now handles data conversion consistently across remote connections. The change simplifies maintenance across several business apps without changing everyday user workflows.

They are no longer needed as the serialization of several Odoo objects
over JSON/XML rpc is now global

Depends on https://github.com/odoo/odoo/pull/35595

This update modernizes internal automated tests by replacing older testing helpers and browser test naming. It helps keep the test suite maintainable and aligned with current browser testing tools, with no expected impact on day-to-day users.

Remove deprecated helpers and rename phantom_js to browser_js.
Enterprise counterpart of https://github.com/odoo/odoo/pull/34011

This update adjusts how the Documents app connects shared behavior across its list, kanban, and inspector views. It should make the document interface easier to extend and maintain, with limited direct impact on day-to-day users.

The Sign app’s JavaScript files were reformatted using the correct linting setup. This is an internal cleanup that improves code consistency and maintainability without changing user-facing behavior.

On commit 375f8a4d6e446ef433eb9c2e0510a10addbe6c91, ESlint was used to clean
the js files in sign. However, one setup from prettier was not used. This
commit runs the correct lint configuration on the files.

The disallowed expenses reporting logic has been reorganized to make the accounting reports easier to maintain and support. This should help improve reliability for finance teams without changing day-to-day workflows.

Field service sales now calculate discounts automatically as part of the normal pricing process instead of relying on a separate manual trigger. This reduces internal complexity and helps keep sales order line discounts consistent without changing the visible workflow for users.

Task-ID-2180180

The systray menu has been rebuilt using Odoo’s newer interface framework to support future improvements. This is mainly an internal modernization, with related updates to enterprise and Studio menu behavior to keep user interactions working correctly.

PURPOSE
Prepare future for OWL

SPEC
Convert Systray Menu into OWL

TASK 2340574

The user menu in the main navigation and mobile interface has been rebuilt on Odoo's newer interface framework. This is an internal modernization that helps keep the product maintainable and ready for future improvements, with little expected change for day-to-day users.

PURPOSE
Prepare future for OWL

SPEC
Convert UserMenu of Systray into OWL

TASK 2329195

Odoo Studio code has been reorganized so business rules live in model components instead of controller entry points. This makes the module easier to maintain and reduces the risk of future changes causing unexpected behavior, without introducing a direct user-facing feature change.

**PURPOSE**
To keep business logic separate, some controller code is moved to model.

**LINK**
2007296

The company switcher has been reorganized so the mobile experience reuses the same menu behavior as desktop. This makes the interface more consistent across devices and should simplify future maintenance without changing core business workflows.

Enterprise part of the company switcher widget refactoring.
The main idea is to reuse the "dropped menu" of the desktop
widget as the mobile widget.

Task 220560