**Problem:**
Since this PR https://github.com/odoo/odoo/pull/261798, both cogs lines have an 
analytic account, which causes the cogs 
to not appear on the project profitability 
report because cogs lines balance each other

**Steps to reproduce:**
- enable 'anglo saxon accounting' and 'analytic accounting'
settings
- create a storable product with automated std 
category, a cost of 10 and on hand quantity
- create a service product and set the 
'create on order' field to 'project'
- confirm a SO for 1 unit of the product and 
1 unit of the service
- validate the delivery and create and confirm invoice
- from the sale order, click on the project smart button
- from the project click on the dashboard smart button

**Current behavior:**
the cogs section don't appear in the profitability report

**Expected behavior:**
it should appear with a line with a value of -10

**Cause of the issue:**
since this PR https://github.com/odoo/odoo/pull/261798, both 
cogs line are linked to the analytic account. 
That's the expected behaviour but in the case of 
the project profitability reports, it prevents the user 
the see the cost of the product in the cogs section.

That's because, inside the 
_get_revenues_items_from_invoices() method, 
bot cogs_line are added to the cogs_line list.
https://github.com/odoo/odoo/blob/141cb292dc5e456161119e19f7a91665feaa0198/addons/sale_project/models/project_project.py#L699-L700

So when computing the amount_to_invoice for 
the costs ml_type, the balance of the lines 
will zero out each other and amount_to_invoice 
will be 0.
https://github.com/odoo/odoo/blob/141cb292dc5e456161119e19f7a91665feaa0198/addons/sale_project/models/project_project.py#L703-L716

As a consequence, the cost of goods sold 
section won't be created
https://github.com/odoo/odoo/blob/141cb292dc5e456161119e19f7a91665feaa0198/addons/sale_project/models/project_project.py#L718-L719

**fix:**
only the line with an account of internal type 
'expense' reflects the actual cost of the product 
sold in the context of the project.
So when computing the profitability report 
that's the only line we should consider

**test:**
test_report_invoice_items_anglo_saxon_automatic_valuation
checks that the cogs section is well displayed in the 
project profitability report.
In the PR (mentionned above) which sets the analytic 
account on the stock cogs line, lines were  
added in the test to manually remove the analytic 
account on the stock cogs line to make the test pass.

With the fix of this PR we can remove those additional 
lines in the test and it will check our use case well again.

opw-6412409

Forward-Port-Of: odoo/odoo#283144

Steps to reproduce:
===================
1. Add a video (e.g. a YouTube URL) to a product from the Sales app.
2. Open the product page on the website.
3. Slide the carousel to the video.

=> The video preview cover is blurry.

Root cause:
===========
The product images are rendered in a carousel (the shop_product_carousel template in ) where only the first slide  gets the "active" class; https://github.com/odoo/odoo/blob/af1b3ee2e7ac56a35bff5e030c3a831c27dbcf24/addons/website_sale/views/templates.xml#L3224-L3226 every other slide is "display: none".
A product video is rendered as a live <iframe> inside its slide, so when the video is not the first media its iframe loads while its container has no  dimensions (0x0). The embedded player then initializes as a small mobile player and loads a low resolution cover thumbnail (120x90), which looks blurry once the slide is shown at full size. Reloading only the iframe while the slide is visible fixes it, a full page reload does not.

Fix:
====
Defer loading the video iframes located on hidden slides their src is moved to a data-src attribute on start and restored once the slide becomes visible. The player then initializes at full size and loads a high resolution cover.

opw-6349394


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

Forward-Port-Of: odoo/odoo#274002

#### Steps to reproduce:
- In an editor field, select some text.
- Type `/` to open the powerbox: the selected content gets deleted.
- Apply any command, e.g. `Separator`.

=> Error: Selection is not in editor

#### Description of the issue this PR addresses:
- `makeSavePoint` overwrites the preserved cursors with the selection staged on the last reverted step, then re-applies the draft mutations. Here those mutations are the deletion of the selected content, done by `onBeforeInputInsertText` before `SearchPowerboxPlugin.onBeforeInput` makes the savepoint. Re-applying them removes the very nodes the staged selection points to, so the cursors end up detached.

#### Desired behavior after PR is merged:
- Only reset the cursors when there is no draft mutation, so the initially preserved selection is restored instead.
- This check added in 19.0 [1], but it isn't in 18.0 to saas-18.4.

[1]: https://github.com/odoo/odoo/pull/244758

task-6442210

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

Forward-Port-Of: odoo/odoo#282162

Clicking the translate button saves the form's root record before opening the translation dialog, since https://github.com/odoo/odoo/commit/9da52919a03dbcee5209430918195158c0652099. A record opened in an x2many form dialog keeps its changes for itself until the dialog is saved, see https://github.com/odoo/odoo/blob/242f6d3cf7288853f163ac6986a3b7aa4279efaf/addons/web/static/src/model/relational_model/static_list.js#L193. Its pending changes are not part of the root record changes, so saving the root sends nothing to the server, and the translation dialog then shows the stored terms instead of the current content, or no terms at all when the stored value is empty.

The fix changes openTranslationDialog in translation_button.js, the place that decides which record to save. When the record keeps its changes for itself (record._noUpdateParent), the record is saved directly, like the button did before the commit above. The root record is still saved in the other cases, so the editable list case that commit fixed keeps working.

Steps to reproduce:
1. Activate a second language in Settings > Translations > Languages
2. Open the Surveys app, open a survey and click a question in the Questions tab
3. In the Description tab, change the description
4. Click the EN button on the description field

=> the translation dialog shows the terms of the previous description, not the current one

Ticket [link](https://www.odoo.com/odoo/project.task/6237291)
opw-6237291

Forward-Port-Of: odoo/odoo#269507

Steps to produce:
---
- Install `sale_management` and `sale_loyalty` module without demo.
- From sales > products > discounts & loyalty, create new loyalty card program and save.
- Now create new product of 100$.
- Create a user which have sales rights as `user: own documents only`.
- With that user, create new sale order with product and confirm.
- Try to cancel the order.

Issue:
---
- It shows the access error: 
```py
You are not allowed to delete 'Sale Order Coupon Points - Keeps track of how a
 sale order impacts a coupon' (sale.order.coupon.points) records.

This operation is allowed for the following groups:
	- Sales/Administrator

Contact your administrator to request access if necessary.
```

Root cause:
---
- Users with the `Sales: Own Documents Only` access right only have read permissions ([1]). When they cancel a Sales Order, the `_action_cancel` method attempts to clean up the temporary pending points allocated to the order by calling `self.coupon_point_ids.unlink()`. Because this call is executed without elevated privileges, the system blocks the deletion and raises an Access Error

Solution:
---
- Added `.sudo()` to the `unlink()` call for `coupon_point_ids` in the `_action_cancel` method. This ensures the pending point records are cleaned up with the necessary elevated privileges.

[1]https://github.com/odoo/odoo/blob/23af2b443735c6d3a2f64e44f9ea5da45638b052/addons/sale_loyalty/security/ir.model.access.csv#L16

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

Forward-Port-Of: odoo/odoo#283535
Forward-Port-Of: odoo/odoo#281477

The aim of this commit is to allow customer to make their batch payment
without facing a Traceback.

Context:
odoo/enterprise@35f5341b9b44cc16eaea311295a064189dd802cb introduced bug
during a badly handled forward port.
The method was removed in saas-18.3 in favor of a function. The forward-port
was half handled and now surfaces to Odoo's own production.

Generating a batch payment could generates the following Traceback:
```py
  File "/home/odoo/src/enterprise/saas-19.3/account_iso20022/models/account_journal_sepa_ct.py", line 69, in _get_PstlAdr
    return super()._get_PstlAdr(partner_id, payment_method_code)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/odoo/src/enterprise/saas-19.3/account_iso20022/models/account_journal.py", line 501, in _get_PstlAdr
    CtrySubDvsn.text = self._sepa_sanitize_communication(partner_address['state'][:35])
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'account.journal' object has no attribute '_sepa_sanitize_communication'
```

Task-id: None (internal issue)