Fix the import of vendor bills that use per-line ScontoMaggiorazione.
The discount/surcharge should be applied to the price unit before taxes, instead of summed and subtracted from the total.

#### Correct
| Product   | Qty | Unit Price | Discount | VAT % | Formula                          | Total     |
|-----------|-----|------------|----------|-------|----------------------------------|-----------|
| Product 1 | 2   | 5.00       | 3.00     | 22%   | `2 * (5 - 3) * 1.22`             | 4.88      |
| Product 2 | 1   | 10.00      | 3.00     | 10%   | `1 * (10 - 3) * 1.10`            | 7.70      |
|           |     |            |          |       |                                  | **12.58** |


#### Before 
the scontomaggiorazione is not managed line by line.
We have to manage line by line because the ScontoMaggiorazione should decrease the "Imponibile" and than calculate the amount tax line by line because each line can have different tax % .

ATTENTION: the ScontoMaggiorazione on ImportoTotaleDocumento is not the sum of the ScontoMaggiorazione on the lines. It is a discount on the amount tax included

Forward-Port-Of: odoo/odoo#206238

In the Time Off app dashboard, employees can view whether some of their unused time off days are set to expire and the exact expiration date.

At the accrual plan level, a validity period can be defined for carried-over days, after which they expire. However, the expiration date of these carried-over days hasn't been considered when calculating the employee's expiring balance.

Steps to reproduce:  
1. Create a new accrual plan.  
2. Define a new accrual plan level.  
3. Configure the level to accrue 10 days annually.  
4. Set the carryover validity to 2 months.  
5. Keep all other settings as default.  
6. Create a new allocation.  
7. Apply the previously defined accrual plan.  
8. Set the start date to 01/01/20xx (where xx is the previous year).  
9. Confirm the employee's balance is now 10 days.  
10. Navigate to the dashboard.  
11. Set the date to 01/01/(20xx + 2), corresponding to the carryover date.  
12. Notice that no expiration date is displayed on the dashboard.  
13. The expiration date should be displayed as 01/03/(20xx + 2).

This update addresses the issue by incorporating the expiration dates of carried-over days into the calculation.

task-4207987

Forward-Port-Of: odoo/odoo#209992
Forward-Port-Of: odoo/odoo#181502

The adaptations from [1] and [2] added some code to the snippet preview
dialog, mainly to adapt text highlights in the snippets content
(starting from `18.0`) and enable the snippets preview interactions
(starting from `18.3`) [A].

In a runbot test context, the snippet selection happens too fast that
the code from [A] (linked to the async behaviour of `insertSnippets`)
can still process the snippets dialog `iframeDocument` (lost after the
dialog being closed on snippet selection).

The goal of this commit is to fix this behaviour by simply taking into
consideration the fact that the preview content can be lost (since in
a real use case, a user will select a snippet in a reasonable time).

[1]: https://github.com/odoo/odoo/commit/1aaf483c5d3b8e8816cfbea7da96ac007a42d492

[2]: https://github.com/odoo/odoo/commit/e008c92fcad2b8cc160586ba6ab94bc077b9bf3d

Remark: This commit will be adapted on `18.3` to fix the code from [2].

runbot-190596

Forward-Port-Of: odoo/odoo#210295

### Steps to reproduce:
	- Navigate to Recruitment > Job Position > Any job position > Job applications (smart button)
	- Create an applicant
	- Set a Recruiter for the applicant
	- Move the stage to 'Contract Signed'
	- Click on 'Create Employee'
	- Notice a validation error that the opertion cannot be completed

### Cause:
This is happening as the 'Job applications' smart button has default value for the user_id in context

https://github.com/odoo/odoo/blob/889f25f1322f00dff7cacad95236d6f045c30d64/addons/hr_recruitment/views/hr_job_views.xml#L207-L211

so when creating an employee it will add the missing fields from defaults and it will get the default value in the context which for an existing user so when creating the employee with this user_id it will trigger the sql constraint

https://github.com/odoo/odoo/blob/889f25f1322f00dff7cacad95236d6f045c30d64/addons/hr/models/hr_employee.py#L145-L148

### Fix:
clean the context before creating the partner and the employee corresponding to this applicant

opw-4629219

Forward-Port-Of: odoo/odoo#211468
Forward-Port-Of: odoo/odoo#204997

Issue Before This Commit:
============================

In MO barcode interface, the by-products section displays the
source location instead of the destination location for each by-product line.
This is misleading, as by-products are outputs of a production
process and should reference a destination location.

Steps to Reproduce:
============================

- Install the stock_barcode_mrp module.
- Activate multi-step routes and By-Products.
- Create a Manufacturing Order with by-products.
- Open the MO using the barcode app.
- In the by-product section notice that:
  - The lines are grouped by Source Location.
  - If you edit by-product line then user has option to edit source location.
  - If the MO operation type has Source Location scan as mandatory,
    user can't edit by-product line.

With This Commit:
============================

- By-product lines are now grouped by their destination location.
- The destination location is displayed for each by-product line.
- The source location field is hidden when editing by-product lines.
- Even if the MO operation type has Source Location scan as mandatory,
  users can still edit by-product lines.

This fix improves clarity and usability for production operators by ensuring
that the appropriate location context is accurately displayed and
can be edited when necessary.

task - [4654161](https://www.odoo.com/odoo/my-tasks/4654161)

Forward-Port-Of: odoo/enterprise#86564
Forward-Port-Of: odoo/enterprise#83617