Currently, updating a POS appointment reservation from the gantt view to increase the number of people does not update the allocated resources. The booking modification is not saved and the UI appears unchanged.

Steps to Reproduce:
1) Install Restaurant and Appointments app with a demo. Enable booking for the restaurant 
2) Open POS restaurant and go to Booking, switch to Gantt view. 
3) Create a reservation for 2 people on a table with capacity 2. 
4) Edit the booking to 4 people and add another table with capacity 2 and save. 
5) The reservation remains at 2 seats and changes are lost.

Root cause:
After [this commit](https://github.com/odoo/enterprise/pull/81810/commits/e710cebceab096f48e044b5b0229de743a204864), the field `waiting_list_capacity` was introduced but the write() method was not present to propagate this value to
`resource_total_capacity_reserved`, causing incorrect capacity computation in the `_inverse_resource_ids_or_capacity` method at [1].

FIX:
Add `write()` to propagate `waiting_list_capacity` into `resource_total_capacity_reserved` to ensure correct recompute and resource update.

[1]- https://github.com/odoo/enterprise/blob/763b34029253a786d1e4bf09a780c1fb799f0ba5/appointment/models/calendar_event.py#L265-L266

Before Fix:
<img width="1911" height="965" alt="image" src="https://github.com/user-attachments/assets/1470c656-7e8b-42bc-96c5-1fd240489ec0" />

After Fix:
<img width="1909" height="961" alt="image" src="https://github.com/user-attachments/assets/ce3b1a46-4e33-42f8-a902-461e05220c23" />


Note:
This fix needs to be merged only in versions 18.3 and 18.4. since in version 18.0-18.2 and 19.0 the `resource_ids` is calculated based on `resource_total_capacity_reserved`(for 18.0-18.2) and `total_capacity_reserved`(for 19.0).

opw-5354559

**PROBLEM**
With a Mexican company, when trying to send a CFDI with a global discount, it can happen that after the repartition of the discount we have lines with a negative amount, so we can't send the CFDI.

**STEP TO REPRODUCE**
1. Take a Mexican company
2. create a quotation with, product A = 1$, product B = 100$, global discount of 15%
3. create an invoice using this quotation, confirm it and try sending the CDFI.
4. the following error will appear : "Error when sending the CFDI to the PAC: Failed to distribute some negative lines"

**CAUSE**
In account, the function `_normalize_target_factor()` takes a list of dictionary `target_factors`, with the keys being invoice lines (the targets) and the keys being weights (the factors). It is used to normalize the weight associated with the lines, to later use them to dispatch things like discounts to those lines. This function also does a sort on the weight, and return a list containing pairs of index and weights. This is useful only in the function `_distribute_delta_amount_smoothly()`, other functions doesn't work well with the sorted returned list: they don't use the index, and dispatch discounts to the wrong lines.

https://github.com/odoo/enterprise/pull/101109 adds a test in l10n_mx to reproduce the client use case.

**Steps to reproduce:**
- Go to a Contact
- Go to the actions dropdown menu of the record
- Grant Portal Access
- Revoke that Access
- Create a new Website in the same Company that Portal Access was granted
- That Contact's user will be set as the Public User for the new Website
- New orders and other default public user behavior will be assigned to this user
- The user will be mentionned in non-logged interactions

**Issue:**
Archived portal user are set as public user when revoked, and the default public user of a website is set on create to the first public user it finds in `_get_public_user`:
```
public_users = self.env.ref('base.group_public').sudo().with_context(active_test=False).users
public_users_for_company = public_users.filtered(lambda user: user.company_id == self)

if public_users_for_company:
    return public_users_for_company[0]
```

This seems to be an issue as such user can be reactivated or be assigned to some transactions it has not made (confidentiality issue).

**Fix:**
Not sure of the best way to fix this. We could ensure new website always creates a new public user, or find a better way to use by default the `self.env.ref('base.public_user')` (or its company-specific copies) for the company of the website during creation (or in `_get_public_user`).

For now the fix remove the public group on the revoked portal user, to still be able to reactivate it later on, without mistaking it for the default public user of a company.

Also we can't remove the `with_context(active_test=False)` as default public user always seems to be disabled.

related: https://github.com/odoo/odoo/commit/83e22fd0636748c4fe1058fb93adfad2623fc31b

opw-4760550

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

Forward-Port-Of: odoo/odoo#236014
Forward-Port-Of: odoo/odoo#233757

## Reproducing steps
1. Create a DB with demo data (hr,hr_payroll,accountant modules)
2. Set the bank account of Mitchell Admin (in Personal employee notebook page): create a new one by specifying the account number (here is a random account IT22M8576110068R4A56E760901) and setting it as "trusted")
3. Set the bank account of the Internal Revenue Service (IRS) partner (also set it as trusted, and here is another random account: IT77H400725028682A0R202P050)
4. Create a new Off-Cycle Payslip : 
a. Payroll -> Payslips -> Payslips -> New Off-Cycle button
b. Set Mitchell Admin as the employee of the payslip
c. Change the Structure to "United States: Regular Pay"
d. Compute Sheets
5. Create payments :
a. Go to the Journal Entries linked to the payslip, and Post them
b. Go back to the payslip and 'Pay'
c. In the new wizard: Click on 'Create Payments'
6. Go back to the journal entries, a new button should've appeared on top of the page for the payments (click it now!)
7. Click on the PAY00001 (it the Federal Income Tax which is made to the Internal Revenue Service (ISR) and notice that the bank account used in payment is the bank account of the employee (should be the ISR account obviously)

## Purpose
Avoid payment wrong initialization when a default value has been set to initialize the `account.payment.register`. Indeed, the `account.payment` also has a `partner_bank_id` property, and so the method `_create_payment`of the `account.payment.register` can initialize payment with wrong `partner_bank_id`.

[enterprise#99373](https://github.com/odoo/enterprise/pull/99373)
[task-4979220](https://www.odoo.com/odoo/action-4043/4979220)

Forward-Port-Of: odoo/odoo#235475

## Reproducing steps
1. Create a DB with demo data (hr,hr_payroll,accountant modules)
2. Set the bank account of Mitchell Admin (in Personal employee notebook page): create a new one by specifying the account number (here is a random account IT22M8576110068R4A56E760901) and setting it as "trusted")
3. Set the bank account of the Internal Revenue Service (IRS) partner (also set it as trusted, and here is another random account: IT77H400725028682A0R202P050)
4. Create a new Off-Cycle Payslip : 
a. Payroll -> Payslips -> Payslips -> New Off-Cycle button
b. Set Mitchell Admin as the employee of the payslip
c. Change the Structure to "United States: Regular Pay"
d. Compute Sheets
5. Create payments :
a. Go to the Journal Entries linked to the payslip, and Post them
b. Go back to the payslip and 'Pay'
c. In the new wizard: Click on 'Create Payments'
6. Go back to the journal entries, a new button should've appeared on top of the page for the payments (click it now!)
7. Click on the PAY00001 (it the Federal Income Tax which is made to the Internal Revenue Service (ISR) and notice that the bank account used in payment is the bank account of the employee (should be the ISR account obviously)

## Purpose
Modifying `account.payment.register` for fixing `hr.payslip` payments generation so that each payment is assigned the correct `partner_bank_id`.

Also, fixing a SEPA payslip payment bug which says that the employee bank account is untrusted even if it isn't. 

## Tests
Adding `test_bank_account_partner_payment_payslip` test to check that the payment generated for Professional Tax is made to the correct bank account (before this fix, the selected account was always the employee bank account, whatever the vendor specified in the payment).

Adding `test_sepa_payslip_partner_bank_id` test to check that the `partner_bank_id` is set after account_register_payment wizard has been initialized and that the action_create_payments (action launched when the user clicks on "Create Payments" button of the `account_register_payment` wizard) doesn't raise any error.

This second test is not really specified in the specs, I just stumbled upon some stacktrace when coding this PR and decided to add a test to check the flow of sepa payment.

[community#235475](https://github.com/odoo/odoo/pull/235475)
[task-4979220](https://www.odoo.com/odoo/action-4043/4979220)

Forward-Port-Of: odoo/enterprise#99373

### Issue:
When installing "l10n_tr_nilvera" on a new DB the Turkish language is installed but
the translation of previously installed modules are not updated.

### Steps to reproduce:
- Install 'l10n_tr_nilvera' and switch to a Saudi company
- Check the view "report_invoice_document"
- Click the translation icon on the view
- No Turkish translations are loaded

### Cause:
When installing "l10n_gcc_invoice" the Arabic language is installed ([src](https://github.com/odoo/odoo/blob/70404624d7ea6f971182cbe4f4fe8fc064d2afd8/addons/l10n_gcc_invoice/__init__.py#L4-L5)). But the method [`_activate_lang()`](https://github.com/odoo/odoo/blob/70404624d7ea6f971182cbe4f4fe8fc064d2afd8/odoo/addons/base/models/res_lang.py#L161-L169) only activates the language, it does not update the translations.

### Solution:
Create a new method that activate the language and calls `_update_translations()` on the installed modules.

opw-5219783

Forward-Port-Of: odoo/odoo#239310
Forward-Port-Of: odoo/odoo#237041

This commit fixes three issues occurring when editing nested `s_card` snippets.

**Problem 1 - Incorrect cover image detection**

Issue: An `s_card` without a cover image displayed the cover image option if it contained a child `s_card` with a cover image.
Cause: The `querySelector` in `CardImageOption` could detect images inside child snippets.
Fix: Now the `querySelector` only searches among direct children of the snippet root element.

**Problem 2 - Ratio settings applied to all child cards**

Issue: Changing the cover image ratio on an `s_card` applied the setting to all nested cards.
Cause: The `we-select` in `s_card` options targeted `.o_card_img_wrapper`, causing the class to apply to all descendants.
Fix: The selector is now `>.o_card_img_wrapper`, so the option acts only on the current snippet.

**Problem 3 - Parent image positioning leaking to children**

Issue: Adjusting the cover image position on a parent `s_card` affected the rendering of all child card images.
Cause: CSS rules for `.o_card_img_horizontal` applied to all descendant elements matching `.o_card_img_wrapper`.
Fix: The rules now apply only to direct children of `.o_card_img_horizontal`. The same correction was applied to `.o_card_img_ratio_custom`.

task-5349540

Forward-Port-Of: odoo/odoo#239503
Forward-Port-Of: odoo/odoo#237587

Steps to reproduce:
===================
1. On an event, make sure to:
- Have at least one paying ticket;
- Remove any "name" or "email" type of question.
2. Go to the event website page as a public visitor and buy one ticket.
   Fill in the form and click on "Go to payment".

-> Nothing happens.

Cause:
======
Clicking on "Go to payment" triggers the registration_confirm function:
https://github.com/odoo/odoo/blob/e91c3817574af8bd48a634e3fb0b2f0e08b21ee9/addons/website_event_sale/controllers/main.py#L78

Triggering `_create_or_update_address` for the first time will create
a partner without a `name`:
https://github.com/odoo/odoo/blob/fa137d08669db2f10cf735a2bc1278b3f1b4f5a9/addons/portal/controllers/portal.py#L543

When clicking on the confirm button, it will re-trigger
`_create_or_update_address`. At that moment, `partner_sudo.name` is
`False`, so the confirmation breaks on: `partner_sudo.name.strip()`
because you cannot call `.strip()` on a `False` value.

Solution:
=========
If the name is not set, simply treat it as unchanged and continue.
In the registration form, a name should normally be provided by default.

opw-5357924

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

### Steps to reproduce:

- With Admin open a pos session
- With an other user without pos access rights archive a product unrelated to pos (e.g. not used in the session)
#### > Access error: You are not allowed to access 'Point of Sale Session' (pos.session) records. This operation is allowed for the following groups: - Point of Sale/User

### Cause of the issue:

Since 985fd5821fe1e8633503d713f1f1c3650bcf0c91 the `action_archive` of products, check that the product is not used by an order of any opened `pos.session` before allowing the user to archive it: https://github.com/odoo/odoo/blob/2011885246f5473ddc16fe5bd17db98ebff712f3/addons/point_of_sale/models/product_product.py#L51-L53 https://github.com/odoo/odoo/blob/2011885246f5473ddc16fe5bd17db98ebff712f3/addons/point_of_sale/models/product_template.py#L313-L320 However, if the user does not have any pos access rights he can not access the pos session to check if the product is used which raises an access error even if the product is un-used.

### Note:

This is notably problematic as it makes it impossible to archive products via the `action_archive` in unrelated stock tests relying on a non-admin user.

opw-stock-tests

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

Steps to Reproduce
===================
1. Upload more than 40+ files in a folder. (One page displays upto 40 docs)
2. Use the checkbox to select all files on the page (this selects only 40 files)
3. Click the 'Select All' button in the control panel to select all 40+ files.
4. Now, try duplicating or moving them to the trash.
=> Only the first 40 selected files (on the single page) are considered for
   action, not all the selected files.

Technical
==========
For documents control panel action we have custom handling for selecting records
and executing action. We use `model.root.selection` which only consider records
in current page, case of select all records from other pages is missed here.

After this PR
==================
- All selected records are considered for the actions
- Added custom `getResIds` method to get filtered `resIds` as per domain.

Note: `getResIds` in DynamicList doesn't have custom domain feature so create
our own as per use case

Task-4700841

Forward-Port-Of: odoo/enterprise#100496
Forward-Port-Of: odoo/enterprise#87634