The field `employee_salary_amount_is_percentage` is computed, but the computation[^1] relies on `hr_employee.salary_distribution`, a field restricted[^2] to members of `hr.group_hr_user`.

If you try to check a bank account without an hr group, you will get an access error:
```
odoo.exceptions.AccessError: You do not have enough rights to access the field "salary_distribution" on Employee (hr.employee). Please contact your system administrator.

Operation: read
User: 21
Groups: allowed for groups 'Employees / Officer: Manage all employees'
```

This also happens during the mock crawl test of upgrades if the admin lacks the group.

To reproduce in standard:
- Install contacts and hr.
- Use a user without hr permissions.
- Try to create a new bank account.

[^1]:https://github.com/odoo/odoo/blob/57573994313988837d89329d77ab1def63a8cfdd/addons/hr/models/res_partner_bank.py#L26
[^2]:https://github.com/odoo/odoo/blob/57573994313988837d89329d77ab1def63a8cfdd/addons/hr/models/hr_employee.py#L147
---

I've also added another commit to make the percentage symbol stick to the salary amount.
Before:
<img width="366" height="38" alt="image" src="https://github.com/user-attachments/assets/ef890852-50ca-40b1-8c09-07c4aa2d330d" />
After:
<img width="219" height="35" alt="image" src="https://github.com/user-attachments/assets/88e4a6c4-bc3f-483e-97f9-3080c6aa85c9" />
I know the number is not formated correctly but I don't think I can do more just from the view.

Forward-Port-Of: odoo/odoo#239298

This commit fixes an issue in the Salary Calculator where all fields were displayed as empty when selecting an employee with a resource_calendar_id set.

Steps to Reproduce :
First Change to either the default company (MyCompany) or Demo Belgian company
Payroll -> Employee -> Salary Calculator -> choose an employee.

Bug : All fields in the Salary Calculator view are empty (evaluated as False).

Root Cause :

Inside _compute_salary, the method _generate_salary_simulation_payslip writes on payslip.version_id using:

payslip.version_id.write(new_payslip_vals)

Because the is_simulation_offer key was missing from the context, this write triggered a full payslip computation, generating payslip lines. During this computation, compute_sheet() performs an unlink() on existing payslip lines. Since the Salary Calculator view fields are only cached at that point, the unlink causes the cached values to be lost, resulting in all fields being evaluated as False.

Fix : Ensure that is_simulation_offer is present in the context when writing to payslip.version_id, preventing payslip line generation and avoiding the unintended unlink() during salary simulation.

Task - 5387155

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

Forward-Port-Of: odoo/odoo#241023
Forward-Port-Of: odoo/odoo#239662

Steps to reproduce:
-------------------------
- Upgrade from lower version to 19.0 or higher.
- Start a fiskaly registered company's session.
- Close the session after transactions.

Issue:
-------
- Tax mapping used to send data to fiskaly is not set.
- If have `-` in company name or cash move reason and try to do cash move will give a tb.

Cause:
---------
- When the user's database is upgraded, the taxes already exist and the company is already registered. As a result, `l10n_de_vat_export_data` is never set, and since no tax changes occur, `l10n_de_vat_definition_export_identifier` is also not generated. This leads to incorrect values being sent to Fiskaly during the session closing request, causing errors.
- The cash statement name uses - as a separator, the current structure is `{session_name}-{move_type}-{statement_type}-{move_reason}` set from `_prepare_account_bank_statement_line_vals()` If move_reason or company name contains additional `-` splitting the whole name breaks the expected structure.

Fix:
-----
- We have added a check to identify any taxes that are missing their tax mapping If such taxes are found, we filter them and trigger the logic to set their mappings. However, if the main mapping reference value l10n_de_vat_export_data is not set, we first retrieve and update it. Once this reference is available, we update all taxes that were previously unset and then prepare the correct tax data.
As a result, the first session closing after the upgrade will automatically correct all issues both for customers who have already upgraded and for those who upgrade in the future.
- We first remove the `{session_name}-` prefix, then split the rest. Since move_type and statement_type never contain -, we take them directly not user inputs, and then rejoin everything from index 2 onward to reconstruct the correct move_reason.

Additional fixes:
--------------------
- Some places the limit of characters may exceed than what fiskaly is asking than it can give us an error so restricted all places where needed.
- We don't have check if the settlement is present if not getting id directly may cause error.

help ticket: 5362897, 5367425

Forward-Port-Of: odoo/enterprise#101468

### [FIX] html_editor: unwrap blocks when inserting in editable span

When the ancestors of the selection are not elements supposed to contain
blocks when pasting, nothing was done to remove those blocks. This could
lead to `span` elements containing `p` elements for example.

This commit unwraps the blocks in the pasted content if the block
containing the selection is outside of the `contenteditable`
element that contains the selection. It also fixes the function
`makeContentsInline` that was not robust to containing some nodes
structures.

Steps to reproduce:
- Open `example.com`, and copy "Example" from the first block
- Open website builder in translate mode
- Paste
- Bug: The appearance is weird because the pasted title is not styled
  as translation
- Save
- Bug: The span of translation where the text was pasted has been reset

####
- Open `example.com`, and copy the whole content
- Open website builder
- Move cursor to the bottom of the footer, with the company name
- Paste
- Bug: it inserted a `p` element in the `span`

(non deterministic, depends on the mood of the AI)
- Open website builder in translate mode
- Select some text (more likely to trigger the bug if it includes a line
  break, for example the description in the footer)
- Use the "Translate with AI" tool from the toolbar
- Bug: The appearance is weird because the inserted translation is not
  styled as translation
- Save
- Bug: The span of translation where the text was changed has been reset

opw-5053872
opw-5109137
opw-5136337
task-5222402

### [FIX] website: restrict inserted content in translate mode to whitelist

The translate mode of the website builder should only ever insert
nodes with a tag in the `TRANSLATED_ELEMENTS` whitelist or with
`o_translate_inline` class inside a translation span. Doing otherwise
makes the translation span "invalid" according to the server, which
discards the translation.

Blocks are already unwrapped when inserting in translations (by the
previous commit), but some other nodes are not in the whitelist, for
example `img`.

This commit adds the class `o_translate_inline` on `a` elements when
inserted and unwraps nodes that are not in the whitelist and do not have
that class.

Steps to reproduce:
- Open `example.com`, and copy the link "Learn More"
- Open website builder in translate mode
- Paste
- Save
- Bug: The span of translation where the link was pasted has been reset

####
- Copy an image (or a piece of html containing an image)
- Open website builder in translate mode
- Paste
- Save
- Bug: The span of translation where the image was pasted has been reset

opw-5053872
opw-5109137
opw-5136337
task-5222402

Forward-Port-Of: odoo/odoo#240421
Forward-Port-Of: odoo/odoo#237969