Currently an error is generated when the user tries to send a quotations to the users.

Steps to produce an error:
- Create a new database with demo data and install `sale_management`
- Go to Invoicing > Configuration > Accounting >Taxes
- Create a new tax with a negative percentage, e.g., -10%
- Create a new `Quotation` and add a product line with the above-created negative tax.
- Error is generated when we try to `Send` this `Quotation`

Error: `KeyError: {'is_withholding': False, 'currency': res.currency(8,)}`

This issue occurs because the key `tax_total_grouping_key` is missing from `ubl_values[target_key]`.  As we see at code line [1], there is already a condition intended to continue and avoid accessing the key when `tax_total_grouping_key` is empty. However, this condition is never triggered because `tax_total_grouping_key` is never empty.

The reason is that `tax_total_grouping_key` is populated from `ubl_default_tax_total_grouping_key` method. As shown in [2], this method always returns a value since it uses a static dictionary. Therefore, `tax_total_grouping_key` is guaranteed to have a value, making the empty check ineffective and allowing the code to attempt access to a key that may not exist in `ubl_values[target_key]`.

This commit fixes the issue by accessing `tax_total_grouping_key` from `ubl_values[target_key]` only when it is available.

[1]: https://github.com/odoo/odoo/blob/c620283459d802d06d07900652752d9f5ad3abef/addons/account_edi_ubl_cii/models/account_edi_ubl.py#L537
[2]: https://github.com/odoo/odoo/blob/c620283459d802d06d07900652752d9f5ad3abef/addons/account_edi_ubl_cii/models/account_edi_ubl.py#L99-L110

sentry-7113127232

## Short functional explanation of the error
Let's say we have created a public holiday on a
Saturday, which is out of an employee's schedule
as they work from monday to friday. When trying
to create a payslip for this employee for the
month the public holiday occurs, it will show
an error.

## Reproduction Steps
1. Create a public holiday on a Saturday. Set the Working Hours to a schedule not including
Saturdays. Set the Work Entry Type as Generic
Time Off.
2. Click on the Configuration tab > Time Off Types.
3. Create a Time Off type. Set the Requires Allocation field at No Limit, and the Work
Entry Type field at Generic Time Off.
4. Click on the Management tab, then Time Off.
5. Click on New. Make sure to select an employee who has the same working schedule as the one you
set for the public holiday, and that on their
contract, their Work Entry Source is set to
Working Schedule. Set the Time Off Type field
to the one you just created.
6. Save and click Approve.
7. Go to Payroll. In Contracts, make sure that the employee's contract is running, and that their contract type is Full-Time.
8. Click on the Payslips tab > to pay.
9. Click on New and select the employee for which you just created a time off.

### Expected behavior
The payslip is created.

### Unexpected behavior
An Odoo Error Occurs.

## Origin of the issue
In the code, we don't verify that the holiday
is present in the employee schedule before
computing the name of the payslip:

https://github.com/odoo/enterprise/blob/a7e954dbe4a68b1770341e754101319a89e4de9e/hr_payroll/models/hr_payslip_worked_days.py#L87-L92

We simply check if one holiday exists, which is
the case as a public holiday is applied to
every employee. Therefore, we need one more
check.

__
opw-5269302

Forward-Port-Of: odoo/enterprise#100445

**Issue**
The scheduled end date of a manufacturing order incorrectly assumes that the work center operates 24 hours a day.

**Steps to reproduce**
1. Create a manufacturing order with:
   - A work order with an expected duration of 1440 minutes.
   - A work center configured to work 8 hours per day.
2. Observe that the scheduled end date is computed as if the work center operates 24h/day resulting in an end date 1 day instead of 4 after the starting date.

**Cause**
The [`date_finish` computation](https://github.com/odoo/odoo/blob/680085b55728dcb000e7bb4277bb83b0e4e2ce91/addons/mrp/models/mrp_production.py#L745C1-L746C105)
does not take into account neither the work center’s calendar nor the workorder dependency when estimating the duration.

**Solution**
Use [`_get_first_available_slot`](https://github.com/odoo/odoo/blob/5d75037d4f81d71a50394c3d390c420967766731/addons/mrp/models/mrp_workcenter.py#L332) to consider workcenter availability, inspired from when a [workorder is planned](https://github.com/odoo/odoo/blob/5d75037d4f81d71a50394c3d390c420967766731/addons/mrp/models/mrp_workorder.py#L527) and implements a topological sort to acknoledge the wo dependencies.
**Additionnal note**
- To make the change minimal, if a workcenter of at least one workorder is unavailable, just fallback on the previous computation.
- This commit use assertAlmostEqual for the same reason than https://github.com/odoo/odoo/commit/e6c958ca226bd8ef7e518243c93e40b92b9b5919

opw-5084120

Issue: YouTube has changed its referrer policy to enforce "strict-origin-when-cross-origin". 
Without this, it can throw a 153 error and block the video.

To replicate in runbot ,add "<meta name="referrer" content="no-referrer"/>" to any major page like the main layout or footer. This sets it for the entire page. 
Therefore, to enforce YouTube's calls to have the proper referrerpolicy, I hardcoded it directly.

Fix:
added 'referrerpolicy="strict-origin-when-cross-origin"' to the iframe.

opw-5239363


Description of the issue/feature this PR addresses:
Our website allows for customization, including the ability to modify meta tags. In ticket#523963, the customer added "<meta name="referrer" content="no-referrer" />" which forced all calls to be set with referrerpolicy="no-referrer" when it's required to have 'referrerpolicy="strict-origin-when-cross-origin"' for embeded videos to youtube

Current behavior before PR:
If a customer sets "<meta name="referrer" content="no-referrer" />" on any page, YouTube blocks it on that page; if it's in the header or footer, the entire website is then blocked. 

Desired behavior after PR is merged:
After it now enforces the call to have 'referrerpolicy="strict-origin-when-cross-origin"' even if the tag <meta name="referrer" content="no-referrer" />". Allowing YouTube to be used. 



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

When adding a lot of loyalty programs with discounts to an order the updatePrograms method could be called multiple times in parallel, that would cause an issue where some of the programs were not applied correctly.

Steps to reproduce:
-------------------
* Create 7 loyalty programs that apply on the same product, each with a discount reward of 10%. (Give them different name)
* Create a POS order with 1 unit of that product.
> Observation: Only the 6 first programs are applied.

Why the fix:
------------
The issue is happening because the updatePrograms is called multiple times in parallel, and when coming to this block of code : https://github.com/odoo/odoo/blob/f3e74f9b840efef7c567ba31acd6ac61c79b5d6d/addons/pos_loyalty/static/src/overrides/models/pos_store.js#L182-L188 The last program has 2 coupons in the `couponPointChanges`, so it will proceed to delete all the coupons of the concerned program. To avoid this we use a mutex to ensure that only one call to updatePrograms is happening at a time.

opw-4974788