Versions
--------
- saas-17.4+

Steps
-----
1. Create a pricelist;
2. add a rule using a cost-based formula;
3. add a 50% markup;
4. export pricelist, then delete or archive it;
5. import pricelist;
6. use pricelist on a quotation.

Issue
-----
The markup isn't applied.

Cause
-----
Commit 06d0053763cd added the `price_markup` field to `product.pricelist.item`. Whenever the markup is set/changed, the `price_discount` field is supposed to get set to its negative value. Currently this only happens in an `onchange` method, which does not get called during import: https://github.com/odoo/odoo/blob/9905de54a55b6d77f67772dde7b2d0ea21adaff1/addons/product/models/product_pricelist_item.py#L322-L325

The value of `price_discount` is what eventual price calculations are based on, so if this isn't updated along with `price_markup`, any price mark-up gets ignored.


Solution
--------
Ensure `price_markup` & `price_discount` are consistent with each other on using `_compute_price_markup` and `_inverse_price_markup`.

opw-4282087

The records cache (from `related_models` module) isn't properly linked to the
reactivity of `posmodel`. As a result, some expected rerenderings aren't
executed. An example of this is the `OrderTab`. When a new floating order is
created the `OrderTab` rerenders listing the new order. However, when that empty
order is deleted, the corresponding tab item isn't removed in the list. That is
because the `OrderTab`'s render method isn't properly subscribed to the changes
in `models['pos.order']`. The render subscription doesn't exist because
`models['pos.order'].readAll` isn't reading on the reactive version of the
`records` cache. That is because `get orderedRecords` is pointing to the
non-reactive version of `records`. `get records` exists in `models` and that's
what we should use to properly link it to the reactivity and that `OrderTab`
properly subscribes `models['pos.order']`.

In this PR we are making sure that the methods of `models` (return value of
`createCRUD`) is properly using the `reactive` version of the `records` cache.
We then pass that version to the CRUD methods to ensure continuity of reactivity
in the records.

We also need to make changes in the `OrderTab` template, converting
`floating-order-container` from `id` to `class` since it's being used for each
order. We should not have multiple instances of an id in the html.

TASK-ID: 4369054

Since [commit [1]](https://github.com/odoo/odoo/commit/189a7c96e6e26825dc05c0c6466576fe63aa091e), where the frontend scrolling was moved back out of the
'#wrapwrap', an issue sometimes occurs with the standard effect when
scrolling on mobile page.

Steps to reproduce:

- Go to a website with "e-commerce" installed.
- Use the devtools to display the website on a mobile device (note that
the bug may only occur on certain mobile devices, so it might be
necessary to test several to reproduce it).
- Add a product to the cart and go to the "/shop/checkout" page.
- Try scrolling down.
- Bug: scrolling is blocked.

The bug happens because, when the page starts scrolling with the
"standard" header, there’s a short moment when the header has a
"translate: transform" applied but is not yet "affixed." This creates a
new coordinate system for the header and affects its child elements,
like the "off-canvas mobile" navbar. As a result, the
"off-canvas mobile" navbar temporarily changes the page size, which
causes scrolling issues, especially on mobile devices.

To fix this, we add "display: none" to the "off-canvas mobile" navbar
during this short moment so it no longer affects the page size.

[opw-4303667](https://www.odoo.com/web#id=4303667&cids=1&menu_id=4720&action=333&active_id=1695&model=project.task&view_type=form)
[opw-4305493](https://www.odoo.com/web#id=4305493&cids=1&menu_id=4720&action=333&active_id=1695&model=project.task&view_type=form)

This PR normalizes rendering to improve readability for text elements using the `text-primary` class.

While links benefit from a contrast-check feature [1], elements using `text-primary` rely on `$primary` (color-1) directly, resulting in color inconsistencies between links and text, as well as readability issues.

The addition of "pastel palettes" [2] made this issue even more pronounced.

This PR:
- Adds `text-primary-emphasis` class to `text-primary` elements, taking priority.
- Introduces a contrast-check for `text-emphasis-*` colors, ensuring links and "primary text" share the same color in cases of low contrast. If contrast is sufficient, the default Bootstrap computation is used.
- Ensure that the `$component-active-color` contrast-check function has a color to compute against.

[1] https://github.com/odoo/odoo/pull/58739
[2] https://github.com/odoo/odoo/pull/172463

task-4332082


| `18.0` reference palette | `18.0` pastel palette | this PR pastel palette | . |
|--------|--------|--------|--------|
| ![image](https://github.com/user-attachments/assets/06b2e02a-673b-423c-a161-0bce6b09bc44) | ![image](https://github.com/user-attachments/assets/3682168d-9c46-4a32-a0c8-9557b14b1ba6) | ![image](https://github.com/user-attachments/assets/cfcf31ee-f894-459f-9488-77ad9be93951) | . |
| ![image](https://github.com/user-attachments/assets/ec262732-7271-4430-b5cb-69d6f244248d) | ![image](https://github.com/user-attachments/assets/60e5b6db-d88e-4f3e-998e-632477d6e362) | ![image](https://github.com/user-attachments/assets/f7633f8b-e9af-47ee-bf46-f4c42e411035) | . |
| ![image](https://github.com/user-attachments/assets/96f3034e-1c06-4068-82a1-0a404e9379d5) | ![image](https://github.com/user-attachments/assets/cad0d86e-83df-47f3-8a0f-0405613a6b06) | ![image](https://github.com/user-attachments/assets/0dc870c8-79a0-41fa-9810-ff9f7eea4773) | . |
| ![image](https://github.com/user-attachments/assets/3a1dfad8-2ed4-43f1-b503-627919dae5e1) | ![image](https://github.com/user-attachments/assets/8de26833-b4ad-4866-a5b4-19ae71b38164) | ![image](https://github.com/user-attachments/assets/c3544e3d-a60e-4f00-9ede-9a71b47a20b9) | . |
| ![image](https://github.com/user-attachments/assets/87f6eae1-156e-4291-b1c2-920dd2211b4c) | ![image](https://github.com/user-attachments/assets/22098e1f-43f3-40d1-bc7b-409730e6ada9) | ![image](https://github.com/user-attachments/assets/e88ddbcc-67db-4d43-acd7-f51101e9628e) | . |
| ![image](https://github.com/user-attachments/assets/52d565ba-886e-4b20-9f29-699d3ea6840f) | ![image](https://github.com/user-attachments/assets/1b961d5e-4366-46fd-aca2-4506f9351e18) | ![image](https://github.com/user-attachments/assets/eefeedf4-28b8-4855-b960-2ed7f5d58322) | . |

task-4332082


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

### Contains the following commits:

https://github.com/odoo/o-spreadsheet/commit/a2652c5a2 [REL] 18.0.7 Task: 0
https://github.com/odoo/o-spreadsheet/commit/68e04cdb6 [FIX] action button: use nextProps instead of this.props Task: 0
https://github.com/odoo/o-spreadsheet/commit/88aa2a7e6 [REV] pivot: select pivot cells in composer Task: 4189098
https://github.com/odoo/o-spreadsheet/commit/e84a864f8 [FIX] helpers: Add generic helper to sanitize sheet names Task: 4347719
https://github.com/odoo/o-spreadsheet/commit/de260ca22 [FIX] pivot: handle boolean-like function arguments in `getPivotCellFromPosition` Task: 4207502
https://github.com/odoo/o-spreadsheet/commit/02b6618d8 [FIX] charts: non-invertible matrix returns NaN as predicted data Task: 4328743

Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com>
Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com>
Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com>
Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com>
Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com>
Co-authored-by: Mehdi Rachico (mera) <mera@odoo.com>
Co-authored-by: Rémi Rahir (rar) <rar@odoo.com>
Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com>
Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>

[FIX] documents: fix error when creating vendor bill from split tool

How to reproduce:
- Install documents_account
- In Document App, folder “Finance”, select 2 pdf
- Click on Action -> Merge PDFs
- Click on “Create Vendor Bill”

You get an error “psycopg2.errors.SerializationFailure: could not serialize access due to concurrent update”

The error was caused by the update of the pdf preview during the execution of the action “Create Vendor Bill” (which both update the document). We solve the problem by waiting the execution of the action before executing the rest (especially the update of the preview).

[FIX] documents: fix traceback after some action

How to reproduce:
- Install documents_account
- In Document App, folder “Finance”, select 2 pdf
- Click on Action -> Merge PDFs
- Remove the scissors to merge the 2 documents
- Click on “Create Vendor Bill”

You get the error: Cannot read properties of null (reading "querySelectorAll").

This is the most reliable way to reproduce the problem but that problem occurs also in other circumstances, for example sometimes when moving to trash documents after some other actions.

We solve the problem by returning an empty selection when there are no element.

Task-4381458

Fixed a series of issues related to flexible and fully flexible resource introduced in task 3762895. In this PR, the following issues are fixed in the planning app:

- In dark mode, the progress bar of resources working fully flexible hours had white background instead of transparent. Step to reproduce:
    1. Open the gantt view, create a resource with fully flexible hours and assign it to a task.
    2. The progress bar should not have a white background on dark mode.

- Fully flexible employee Suman Oza had no hourly cost set in demo data. Step to reproduce:
    1. Go to the employees view and search for Suman Oza.
    2. The hourly cost should be no longer be set to 0.

- Flexible employee should have the period outside of their contract grayed in the Gantt view Step to reproduce:
    1. Create a resource with flexible hours.
    2. Set a contract with a start and end date.
    3. Open the gantt view in planning, and search for the resource.
    4. The period outside of the contract should be grayed.

- In gantt view sparse mode view, the color of the progress bar (the thin line above each employee and each day) of resources working fully flexible hours should be always in purple color. Step to reproduce:
    1. Create a resource with fully flexible hours.
    2. Create some shifts for the resource.
    3. Open the gantt view in sparse mode.
    4. The progress bar should be in purple color.

- Recurring shifts for fully flexible employees are now assigned even if they generate conflicts with existing shifts. (test was added to ensure this behavior) Step to reproduce:
    1. Create an employee working fully flexible hours.
    2. Plan some shifts for the employee.
    3. Create a recurring shift for the employee which ovelaps with the existing shifts.
    4. The recurring shifts should be assigned to the employee even if they generate conflicts with existing shifts.

task-id: 4189386

The tax report (KMD report) and annex to the tax report (KMD INF report) for Estonia needed to be reworked to correct errors and fix rounding issues.

With this commit, the tax report:
1. Adds the balance_from_tags to allow auditing the report lines, since only aggregation was used before.
2. Fixes rounding issues by using the integer_rounding feature and adding rounding differences to the VAT closing entry.

This commit also rewrites the KMD INF report. It creates one report composed of two sections with different columns, using the custom engine to construct both parts.

Part A contains information on invoices issued, grouped by move_id and id, to allow showing multiple lines per invoice when different tax rates or special tax types are in one invoice. It only includes invoices with taxable supply at 22%, 20%, 9% and 5%. It excludes invoices of partners whose Tax ID is / and foreigner partners who have a Tax ID not starting by EE.

Part B contains information on invoices received, grouped by move_id. Each line showcases information about one invoice with taxable supply at 22%, 20%, 9% and 5%. It relies on a Tax ID starting with EE.

The reports follow the guidelines available in
https://www.emta.ee/en/business-client/taxes-and-payment/tax-returns-exchange-information/vat-return-forms-vd-and-vdp (forms valid from 01.01.2024 onwards).

task-3997203

steps to reproduce:
- Install documents_account
- In Settings -> File centralization -> Activate "Accounting"
- Then click on Journals below
- Then add Jounal: Vendor Bill, Workspace: Finance
- Then upload a file in the app Documents, in the workspace Finance
- Select that file and update the partner to Azure Interior
- Click on the action "Create Vendor Bill"

The partner "Azure Interior" is not set on the created account move while it should.

For fixing this adding ``partner_id`` of document if present.

Now question may arise why account.move having null partner_id. because it being [set](https://github.com/odoo/enterprise/blob/64fc38a80520cfeeb81c0bb329c6b24c3e9454e1/documents_account/models/documents_workflow_rule.py#L77) after creating [attachment](https://github.com/odoo/enterprise/blob/64fc38a80520cfeeb81c0bb329c6b24c3e9454e1/documents_account/models/documents_workflow_rule.py#L76)
 and during create attachment ``document.partner_id`` is set to null and issue is raised.

opw-4077356